Service design and order fulfillment system

ABSTRACT

A system that designs a fulfillment solution and fulfills an order using the fulfillment solution is provided. The system defines a technical catalog that includes items including metadata used by a fulfillment solution. The system further defines a fulfillment solution blueprint that includes multiple order layers that define multiple layers of the fulfillment solution, multiple provider functions structured according to a dynamic pattern-driven model, and multiple interface contracts defining multiple interactions between multiple provider functions. The system further designs the fulfillment solution to use at least one item of the technical catalog to fulfill an order. The system further designs the fulfillment solution based on the fulfillment solution blueprint. The system further generates the fulfillment solution based on the fulfillment solution blueprint using at least one item of the technical catalog.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority of U.S. Provisional Patent ApplicationSer. No. 61/668,946, filed on Jul. 6, 2012, the subject matter of whichis hereby incorporated by reference.

FIELD

One embodiment is directed to a computer system, and more particularly,to computer systems that provision services, such as communicationservices.

BACKGROUND

Certain computer systems are used in a number of industries, such as thecommunications industry, for order entry and order fulfillment. Orderentry is the process of electronically receiving orders and entering theorders into the computer system, where the orders are stored as one ormore entities within the computer system, so that the orders can beelectronically fulfilled. Orders can contain data regarding one or moreproducts, the pricing of one or more products, and one or more offersrelated to the one or more products. Orders can be received from anytype of customer, such as businesses and individual consumers. Orderfulfillment is the process of electronically fulfilling the orders, oncethe orders have been entered into the computer system. Order fulfillmentgenerally entails one or more of the following steps: validating theorder, interfacing the order to a billing system or subsystem, shippingphysical goods, scheduling installation of equipment, installingequipment, and activating services. Order fulfillment can also entailother steps not listed that are part of a process of electronicallyfulfilling an order.

Faced with industry dynamics that prioritize agility in implementingboth superficial and fundamental changes, the communications industryhas struggled to deploy order fulfillment solutions that supportversatility in a manageable way. Common industry approaches typicallystart with fulfillment solutions that are fundamentally architected toaddress a narrow set of products/services/technologies and incrementallybroaden their capabilities. Getting beyond the limitations of thistypically leads service providers to add entirely new solution stacks toaddress new domains.

SUMMARY

Service design is a process of defining all entities, artifacts, andmetadata used to allow for presenting, browsing, selling, order capture,and order fulfillment of service-based and physical good-based productofferings. In part, service design is about populating a technicalcatalog with entities and metadata used to enable service orderfulfillment.

One embodiment is a system that designs a fulfillment solution andfulfills an order using the fulfillment solution. The system defines atechnical catalog that includes items including metadata used by afulfillment solution. The system further defines a fulfillment solutionblueprint that includes order layers that define layers of thefulfillment solution, provider functions including components of thefulfillment solution, and interface contracts defining interactionsbetween provider functions. The system further designs the fulfillmentsolution to include an item of the technical catalog. The system furtherdesigns the fulfillment solution based on the fulfillment solutionblueprint. The system further generates the fulfillment solution basedon the fulfillment solution blueprint using the item of the technicalcatalog.

BRIEF DESCRIPTION OF THE DRAWINGS

Further embodiments, details, advantages, and modifications will becomeapparent from the following detailed description of the preferredembodiments, which is to be taken in conjunction with the accompanyingdrawings.

FIG. 1 illustrates a block diagram of a system that can implement anembodiment of the invention.

FIG. 2 illustrates a service design and order fulfillment system,according to an embodiment of the invention.

FIG. 3 illustrates a flow diagram of the functionality of a servicedesign and order fulfillment module, according to an embodiment of theinvention.

FIG. 4 illustrates an information model of a technical catalog,according to an embodiment of the invention.

FIG. 5 illustrates a service design that includes a set of entity modelitems of a technical catalog, according to an embodiment of theinvention.

FIG. 6 illustrates a service design that includes an example set ofentity model items and behavior model items of a technical catalog,according to an embodiment of the invention.

FIG. 7 illustrates a service design that includes another example set ofentity model items and behavior model items of a technical catalog,according to an embodiment of the invention.

FIG. 8 illustrates an example set of infrastructure model items of atechnical catalog, according to an embodiment of the invention.

FIG. 9 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention.

FIG. 10 illustrates an example fulfillment solution blueprint, accordingto an embodiment of the invention.

FIG. 11 illustrates an example definition of order layers and topologyfor a fulfillment solution blueprint, according to an embodiment of theinvention.

FIG. 12 illustrates an example definition of provider functions andcontract interfaces for a fulfillment solution blueprint, according toan embodiment of the invention.

FIG. 13 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention.

FIG. 14 illustrates a block diagram of an entity hierarchy, according toan embodiment of the invention.

FIG. 15 illustrates an example product offering and an example productspecification to customer-facing service specification mapping,according to an embodiment of the invention.

FIG. 16 illustrates an example product specification to fulfillmentpattern mapping for an example product offering, according to anembodiment of the invention.

FIG. 17 illustrates an example product specification to fulfillment flowmapping for an example customer order, according to an embodiment of theinvention.

FIG. 18 illustrates an example customer-facing service specification tofulfillment pattern mapping, according to an embodiment of theinvention.

FIG. 19 illustrates an example customer-facing service specification tofulfillment flow mapping for an example service order, according to anembodiment of the invention.

FIG. 20 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention.

FIG. 21 illustrates examples of service order, a customer order, and atechnical order, according to an embodiment of the invention.

FIG. 22 illustrates an example of a plurality of service lines of aservice order, according to an embodiment of the invention.

FIG. 23 illustrates an example customer-facing service specification tofulfillment pattern mapping, where each customer-facing servicespecification is part of a service order line of a service order,according to an embodiment of the invention.

FIG. 24 illustrates an example service order mapped to an examplefulfillment pattern, according to an embodiment of the invention.

FIG. 25 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention.

FIG. 26 illustrates a general form of an action specification for anaction, according to an embodiment of the invention.

FIG. 27 illustrates an example of a service action, according to anembodiment of the invention.

FIG. 28 illustrates two examples of service actions, according to anembodiment of the invention.

FIG. 29 illustrates an example of two technical actions with differingdegrees of specialization, according to an embodiment of the invention.

FIG. 29A illustrates another example of two activation actions withdiffering degrees of specialization, according to another embodiment ofthe invention.

FIG. 29B illustrates an example hierarchy of order lines, according toan embodiment of the invention.

FIG. 30 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention.

FIG. 31 illustrates an example provider function, according to anembodiment of the invention.

FIG. 32 illustrates another example provider function, according to anembodiment of the invention.

FIG. 33 illustrates metadata of an example provider function, accordingto an embodiment of the invention.

FIG. 34 illustrates a transformation sequence of an example providerfunction, according to an embodiment of the invention.

FIG. 35 illustrates an example fulfillment flow for a provider function,where the fulfillment flow is dynamically generated from a fulfillmentpattern, according to an embodiment of the invention.

FIG. 36 illustrates a service design and order fulfillment system thatutilizes a plurality of provider functions, according to an embodimentof the invention.

FIG. 37 illustrates a provider function that utilizes one or more itemsof a technical catalog, according to an embodiment of the invention.

FIG. 38 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention.

FIG. 39 illustrates an example service order calculation providerfunction that transforms a customer order into a service order,according to an embodiment of the invention.

FIG. 40 illustrates an example service order calculation providerfunction, according to an embodiment of the invention.

FIG. 41 illustrates an example transformation sequence that transforms acustomer order into a service order, according to an embodiment of theinvention.

FIG. 42 illustrates an example transformation rule set, according to anembodiment of the invention.

FIG. 43 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention.

FIG. 44 illustrates an example technical order calculation providerfunction that generates a technical order, according to an embodiment ofthe invention.

FIG. 45 illustrates an example technical order calculation providerfunction, according to an embodiment of the invention.

FIG. 46 illustrates an example transformation sequence that generates atechnical order, according to an embodiment of the invention.

FIG. 47 illustrates an example generation of a technical order based ona configuration delta, according to an embodiment of the invention.

FIG. 48 illustrates another example generation of a technical orderbased on a configuration delta, according to an embodiment of theinvention.

FIG. 49 illustrates another example generation of a technical orderbased on a configuration delta, according to an embodiment of theinvention.

FIG. 50 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention.

FIG. 51 illustrates an order management workflow for a service designand order fulfillment system, according to an embodiment of theinvention.

FIG. 52 illustrates an example design of an entity, according to anembodiment of the invention.

FIG. 53 illustrates example process logic structured around an exampledomain entity model, according to an embodiment of the invention.

FIG. 54 illustrates an example creation of process logic for an instanceof a customer-facing service, according to an embodiment of theinvention.

FIG. 55 illustrates an example instance of a customer-facing service,according to an embodiment of the invention.

FIG. 56 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention.

DETAILED DESCRIPTION

According to an embodiment, a service design and order fulfillmentsystem is provided that can flexibly fulfill a wide range of orders,such as communication/information service orders. The system utilizes anarchitectural approach and methodology that includes a technical catalogand a fulfillment solution blueprint. The technical catalog can featurea design for a content, structure, and usage of a technical catalog(i.e., a metadata catalog), where the metadata of the technical catalogcan configure a behavior of a service design and order fulfillmentsystem. The metadata of the technical catalog can drive operationalbehavior following a pattern-driven fulfillment model. The technicalcatalog can include definitions associated with a specification, such asan action or a fulfillment pattern. The fulfillment solution blueprintcan feature: (a) a separation between a commercial layer and a servicelayer; (b) a separation between a service layer and a technical layer;and (c) an orchestration decoupled from a fulfillment topology. Thefulfillment solution blueprint can be defined in terms of: (a) processesand provider functions that follow a pattern-driven fulfillment model,where specific provider functions can include: (1) a provider functionfor calculating a service order; (2) a provider function for calculatinga technical order; and (3) a provider function for designing a serviceby selecting and assembling supporting components; and (b) interfaces,where specific interfaces can include (1) a service order; and (2) atechnical order.

FIG. 1 illustrates a block diagram of a service design and orderfulfillment system 10 that may implement one embodiment of theinvention. Service design and order fulfillment system 10 includes a bus12 or other communications mechanism for communicating informationbetween components of service design and order fulfillment system 10.Service design and order fulfillment system 10 also includes a processor22, operatively coupled to bus 12, for processing information andexecuting instructions or operations. Processor 22 may be any type ofgeneral or specific purpose processor. Service design and orderfulfillment system 10 further includes a memory 14 for storinginformation and instructions to be executed by processor 22. Memory 14can be comprised of any combination of random access memory (“RAM”),read only memory (“ROM”), static storage such as a magnetic or opticaldisk, or any other type of machine or computer-readable medium. Servicedesign and order fulfillment system 10 further includes a communicationdevice 20, such as a network interface card or other communicationsinterface, to provide access to a network. As a result, a user mayinterface with service design and order fulfillment system 10 directly,or remotely through a network or any other method.

A computer-readable medium may be any available medium that can beaccessed by processor 22. A computer-readable medium may include both avolatile and nonvolatile medium, a removable and non-removable medium, acommunication medium, and a storage medium. A communication medium mayinclude computer readable instructions, data structures, program modulesor other data in a modulated data signal such as a carrier wave or othertransport mechanism, and may include any other form of informationdelivery medium known in the art. A storage medium may include RAM,flash memory, ROM, erasable programmable read-only memory (“EPROM”),electrically erasable programmable read-only memory (“EEPROM”),registers, hard disk, a removable disk, a compact disk read-only memory(“CD-ROM”), or any other form of storage medium known in the art.

Processor 22 can also be operatively coupled via bus 12 to a display 24,such as a Liquid Crystal Display (“LCD”). Display 24 can displayinformation to the user. A keyboard 26 and a cursor control device 28,such as a computer mouse, can also be operatively coupled to bus 12 toenable the user to interface with service design and order fulfillmentsystem 10.

According to one embodiment, memory 14 can store software modules thatmay provide functionality when executed by processor 22. The modules caninclude an operating system 15, a service design and order fulfillmentmodule 16, as well as other functional modules 18. Operating system 15can provide an operating system functionality for service design andorder fulfillment system 10. Service design and order fulfillment module16 can provide functionality for designing one or more services and forfulfilling one or more orders using the one or more designed services,as is described in more detail below. In certain embodiments, servicedesign and order fulfillment module 16 can comprise a plurality ofmodules that each provide specific individual functionality fordesigning one or more services and for fulfilling one or more ordersusing the designed services. Service design and order fulfillment system10 can also be part of a larger system. Thus, service design and orderfulfillment system 10 can include one or more additional functionalmodules 18 to include the additional functionality. For example,functional modules 18 may include modules that provide additionalfunctionality, such as an “Oracle Communications Order and ServiceManagement” product from Oracle Corporation. In another example,functional modules 18 may include enterprise resource planning (“ERP”)modules of an ERP system, where an ERP system is a computer system thatintegrates several data sources and processes of an organization into aunified system.

Processor 22 can also be operatively coupled via bus 12 to a database34. Database 34 can store data in an integrated collection oflogically-related records or files. Database 34 can be an operationaldatabase, an analytical database, a data warehouse, a distributeddatabase, an end-user database, an external database, a navigationaldatabase, an in-memory database, a document-oriented database, areal-time database, a relational database, an object-oriented database,or any other database known in the art.

According to an embodiment, an order fulfillment process can include twocomponents: a concept-to-market component, and an order-to-cashcomponent. A concept-to-market component extends from the timecommercial offers based on technical capabilities are conceived to thepoint of readiness to capture orders for such offers and to deliver suchorders. An order-to-cash component supports the business process thatextends from a time a quote or order is captured or generated to thetime where the services and goods are delivered and properly billed.

A service design and order fulfillment system can offer standardizedcapabilities that facilitate easy solution adaptation, integration, andtransformation. A service design and order fulfillment system caninclude the following business support systems (“BSS”) components: acustomer relationship management (“CRM”) component; a central ordermanagement (“COM”) component, a supply chain management (“SCM”)component, and a workforce management (“WFM”) component. A CRM componentcan host many front office capabilities, such as shared services (e.g.,Sales Catalog, Customers, Customer Assets (Utilized Commercial CustomerInventor), Sales Quote and Order Capture, Agreements, and CustomerService) across several channels (e.g., call center, retail, web,social, partner, and messaging. A COM component can support customerorder decomposition, orchestration, and order lifecycle management. ACOM component can interface with one or more fulfillment systems inorder to fulfill a customer order. A SCM component can providefulfillment services, such as physical goods fulfillment and logistics.A WFM component can provide workforce services, such as appointmentscheduling and field installation.

A service design and order fulfillment system can further include thefollowing operations support systems (“OSS”) components: a convergedservice order management (“SOM”) component, a service and resourcemanagement (“SRM”) component, and component. An SOM component cansupport service order decomposition, orchestration, and order lifecyclemanagement. The SOM component can further orchestrate fulfillment of aservice order across one or more SRM components, technical ordermanagement (“TOM”) components, and/or SCM and WFM components. An SRMcomponent supports “design and assign” functionality for a serviceorder, service order transformation to a technology-specific technicalorder, and technical inventory lifecycle management. A TOM componentorchestrates fulfillment of technical orders across several components,such as SCM components, WFM components, and activation components.

A service design and order fulfillment system can further include anenterprise catalog that can support a unified definition-time experienceto define common commercial catalog items to support BSS components, andcommon technical catalog items to support OSS components. The commercialand technical catalogs can make up the enterprise catalog and includeentities such as a product specification, a service specification, suchas a customer-facing service specification and a resource-facing servicespecification, and a resource specification. Such entities can includemetadata that can drive logic in BSS components and OSS components.

Capabilities of a service design and order fulfillment system can beorganized into the following capabilities: product lifecycle management(“PLM”); order lifecycle management (“OLM”); inventory lifecyclemanagement (“ILM”); and customer lifecycle management (“CLM”). Suchcapabilities are now further described in greater detail.

Service providers typically offering their customers services andphysical goods of specific utility for a set price. Significantinvestment typically goes into building a service providerinfrastructure (e.g., network and/or IT elements) before service becomeavailable to offer to customers. The process is often referred to asplan-and-build (“P&B”). To facilitate management of a provider'sinfrastructure, it can be modeled as a set of resources and resourcefacing services. An infrastructure can have affinity to a servicedomain, where a service domain is a set of closely related services thatare used together and typically based on a common set of infrastructureelements. Examples of service domains can include mobile, fixed, cable,software-as-a-service (“SaaS”), and network-based business-to-businessservices. PLM capabilities can facilitate a variety of change scenariosthat assume and build on the outcome of the P&B process. PLM canfacilitate service commercialization and order fulfillment as well asthe lifecycle of all associated entities.

A “resource” is a part of a provider's infrastructure, customer premiseequipment (“CPE”) utilized directly or indirectly by a service, or agood that may be procured by the market in the form of a product. Aresource can be physical and it can be realized through the provider'sinfrastructure or as a CPE. Alternatively, a resource can be logical andit can be realized directly as a configuration (via software) ofphysical resources, or it may be used to facilitate the configuration ofthe network or the interactions with a third-party supplier or partner.Examples of resources include a provider edge router, a handset, anauthentication, authorization, and accounting (“AAA”) account, aninternet protocol (“IP”) address, a modem, a digital subscriber lineaccess multiplexer (“DSLAM”), a digital subscriber line interface (“DSLinterface”), and a virtual machine. A “resource specification” is anentity that represents a type of resource, and can be used to facilitatereuse of attributes and logic associated with one or more resources.

A “resource-facing service” is a technology-specific, vendor-agnosticabstraction of a capability from a perspective of a service provider (asopposed to a perspective of an end user). Thus, instead of directlyexposing a resource to a customer, some sets of resources can becombined together in ways that provide a service. Thus, aresource-facing service represents a meaningful capability associatedwith one or more resources. A resource-facing service may also combinecapabilities from other finer-grained resource facing services. Examplesof resource-facing services include digital subscriber line (“DSL”),data over cable service interface specification (“DOCSIS”), globalsystem for mobile communications (“GSM”), layer 3 virtual privatenetwork (“L3VPN”) and e-mail. A “resource-facing service specification”is an entity that represents a type of resource-facing service, and canbe used to facilitate reuse of attributes and logic associated with oneor more resource-facing services.

A “customer-facing service” is a technology-agnostic abstraction of aholistic capability from a perspective of a service provider (as opposedto a perspective of an end user) that facilitates servicecommercialization, fulfillment and management. A customer-facing servicecan be realized through one or more technical solutions, where atechnical solution is comprised of one or more resources and/orresource-facing services. Thus, a customer-facing service defines theservice related features of commercial value that can be made availableto a market through one or more product offerings. Examples ofcustomer-facing services include broadband, mobile, VPN, and email. A“customer-facing service specification” is an entity that represents atype of customer-facing service, and can be used to facilitate reuse ofattributes and logic associated with one or more customer-facingservices.

A “product offering” is a representation of a definition and commercialattributes (e.g., pricing) associated with a sales catalog item (e.g.,product, service), and a product offering is made available to sell tocustomers. Product offerings can be classified into the following types:simple product offering; bundled product offering; or promotionalproduct offering. A “simple product offering” or “simple offering” is acommercially viable and commercially indivisible sales catalog item. Asimple offering can establish a promise to a customer and can representa variety of commercial items, such as physical goods, services, servicefeatures, discounts, or pricing items. Simple offerings can be madeavailable to sell solo, within a bundled or promotional offering, orboth. Examples of simple offerings can include “iPhone for $300 one-timecharge,” or “1000 Minutes Mobile Plan for $75 monthly charge.” A“bundled product offering” or “bundled offering” is an aggregation ofone or more simple offerings, other bundled offerings, and orcommercialization logic to facilitate selling and contracts. An exampleof a bundled offering is “1000 Minutes iPhone Package” that includes the“iPhone” simple offering and the “1000 Minutes Mobile Plan” simpleoffering. A “promotional product offering” or “promotional offering” isa special type of bundled offering that offers reuse under differentcommercial and contractual terms. An example of a promotional offeringis “Add an iPhone 50% discount and a two-year contract term.” A “productspecification” is an entity that represents a type of product offering,and can be used to facilitate reuse of attributes and logic associatedwith one or more product offerings. More specifically, a productspecification represents all or a subset of the capabilities of acustomer-facing service specification.

As previously described, a service design and fulfillment system canfurther include an enterprise catalog that can support a unifieddefinition-time experience to define common commercial catalog items tosupport BSS components, and common technical catalog items to supportOSS components. The enterprise catalog can include the definition,metadata, and logic associated with items, such as products, services,and resources. The enterprise catalog can further include a commercialcatalog for customer and supply chain perspectives and a technicalcatalog for OSS perspectives. Commercial catalog items can be deployedinto operational time CRM sales catalogs, billing catalogs, SCMcatalogs, and COM catalogs. Technical catalog items can be deployed intooperational time service and resource catalogs, activation catalogs, andservice order management catalogs.

Orders are a primary mechanism to do business and affect change in aprovider's infrastructure. OLM covers a wide right of capabilities thatrelate to orders, and is now described in greater detail. Businesses cangenerate orders for many purposes, where “order intent” is defined as apurpose of the order. Orders can be named after their intent. Forexample, an order generated to purchase goods and services from asupplier is called a purchase order. An order generated to sell goodsand services to a customer is called a sales order. An order generatedto issue a quote to a customer is a quote order.

In certain embodiments, an order can be composed of an order header andone or more order lines (or order items). An “order header” is acomponent of an order that can capture information applicable to allorder lines, such as an order number and customer type. An “order line”can represent an action and a subject that together represents a portionof the order intent. An action represents a request, such as “ADD,”“DELETE,” or “UPDATE” to apply to a subject. A subject refers to anentity that undergoes the action. An example of a subject is a productoffering.

As part of fulfilling the order, the order can be decomposed intoseveral sub-orders, where each sub-order can either have the sameintent, or a different intent, as compared to the intent of the originalorder. In addition, the subject of the one or more order lines can betransformed to different granularities. In the context of thecommunications industry, an order subject can assume one of fourgranularities from an order subject name that are derived as follows:customer order, service order, or technical order. A “customer order” isan order with product offering order line subjects. A “service order” isan order with customer-facing service order line subjects. A “technicalorder” is an order with resource-facing service or resource order linesubjects.

According to an embodiment, order fulfillment can utilize multiple ordersubject transformations via a set of one or more order layers. A firstorder layer can be a customer order layer (also identified as a“customer layer”). Within the customer order layer, a customer order,such as a sales customer order can be captured in a CRM component, orcan be generated within a CRM component by a channel or a third-party.The customer order can be submitted to a COM component, where thecustomer order can be decomposed into a number of order components. Eachorder component is a customer order intended for a BSS or OSSfulfillment function. In fulfilling a customer order, the customer ordercan be transformed to a service order. Customer order to service ordertransformation can be performed by a service order calculation providerfunction identified as “Calculate Service Order.”

A second order layer can be a service order layer (also identified as a“service layer”). A service order layer can start with the generation ofa service order, where a service order can be generated in a COMcomponent, an SOM component, or by a third party. The service order canbe designed, and one or more technical orders can be generated by atechnical order calculation provider function identified as “CalculateTechnical Order.”

A third order layer can be a technical order layer (also identified as a“technical layer”). The technical order can be decomposed into a numberof technical order components, where the technical order components canbe generated by a component, such as an activation component, a SCMcomponent, or a WFM component.

Orders have a life cycle that governs their behavior from inception toexit. Lifecycles are governed by states, logic that determines lifecycleimpacting events, valid transitions between states, and valid behaviorwhile an order is in a given state. Further, orders are generated toaffect change to an existing state. Based on a kind of context of changean order is generated for, an order can be classified as one or moreorder types. Specific order states and order types are not relevant toembodiments of this invention, and thus, specific order states and ordertypes are not discussed in further detail.

In each order layer, each type of order is fulfilled by the servicedesign and order fulfillment system. Order fulfillment topology is nowdescribed in greater detail. A “fulfillment topology” refers to a set ofone or more fulfillment systems, where the fulfillment topology belongsto one or more fulfillment system types, and where the fulfillmenttopology includes one or more fulfillment providers, and one or morefulfillment functions. A “fulfillment system type” is a class offulfillment systems that that can provide a single fulfillment functionor a single class of fulfillment functions. A “fulfillment system”refers to a computer system that can provide one or more fulfillmentfunctions. A “fulfillment provider” is an instance of a fulfillmentsystem. A “fulfillment function” is a unit of fulfillment work providedby a fulfillment system. An “orchestration plan” is made of one or morefulfillment functions along with one or more dependencies. A“dependency” refers to when an execution of a fulfillment functiondepends on the execution of another fulfillment function. A “fulfillmentflow” refers to an entity that includes a set of fulfillment patterns.

According to an embodiment, a COM component can decouple fulfillmenttopology from products and fulfillments flows, and a SOM component candecouple fulfillment topology from services, resources, and fulfillmentflows. This can increase an agility of order fulfillment, reduce costfor maintaining fulfillment flows, and can decrease time to market whenintroducing new products. To keep COM fulfillment flows decoupled fromfulfillment topology, the COM component can recognize fulfillmentsystems by type. For each fulfillment system type, the COM component canrecognize fulfillment functions available for orchestration. Whenexecuting an orchestration plan, the COM component can deploy businessrules that apply topology configurations to decompose the order androute fulfillment function requests to a relevant fulfillment systemprovider. The same concept can be applied to the SOM component and theTOM component, where either the SOM component or the TOM component candecouple fulfillment flow from fulfillment topology.

Order fulfillment is further described in U.S. Patent ApplicationPublication No. 2012/0150676 (herein incorporated by reference), U.S.Patent Application Publication No. 2012/0150583 (herein incorporated byreference), U.S. Patent Application Publication No. 2012/0150692 (hereinincorporated by reference), U.S. Patent Application Publication No.2012/0150582 (herein incorporated by reference), and U.S. PatentApplication Publication No. 2012/0150693 (herein incorporated byreference).

FIG. 2 illustrates a service design and order fulfillment system 200,according to an embodiment of the invention. Service design and orderfulfillment system 200 is a comprehensive system for serviceconcept-to-market and service order to activate process automationcomposed of a number of capabilities that are separately describedbelow. More specifically, service design and order fulfillment system200 is configured to design and generate a fulfillment solution, wherethe fulfillment solution includes a plurality of provider functions, andwhere the fulfillment solution can fulfill an order. Service design andorder fulfillment system 200 includes several components that areseparately described below in greater detail.

According to the illustrated embodiment, service design and orderfulfillment system 200 includes service design component 210. Servicedesign component 210 can be configured to capture and store aspects of abusiness relevant to service fulfillment via metadata, where themetadata is defined and structured within a technical catalog 211.Technical catalog 211 can further populate and attribute resourceinstances in inventory by appropriately defining metadata, in readinessfor use in order fulfillment. The metadata of technical catalog 211 candrive operational behavior following a pattern-driven fulfillment model.The technical catalog can include definitions associated with aspecification, such as an action or a fulfillment pattern. Technicalcatalog 211 is further described below in greater detail. Thus, servicedesign component 210 can support effective definition and management ofdomain information models structured according to a defined structure oftechnical catalog 211.

Service design and order fulfillment system 200 further includes serviceorder delivery component 220. Service order delivery component 220 canbe considered analogous to a group of manufacturing lines, where eachline represents a process within a layer and composed of fulfillmentproviders driven by catalog-provided fulfillment providers. Serviceorder delivery component 220 can be configured to design and generatefulfillment solutions, where fulfillment solutions implement specificprovider functions and communicate via specific instances as describedin a fulfillment solution blueprint 221. Fulfillment solution blueprint221 can include: (a) a plurality of interlocking layers of ordermanagement; (2) a defined set of durable and domain-agnostic providerfunctions, built according to a meta-pattern; and (3) a set of interfacecontracts used between provider functions and order layers, definedaround a unified request concept. Fulfillment solution blueprint 211 canfurther feature a separation between a commercial layer and a servicelayer. Fulfillment solution blueprint 211 can be defined in terms of:processes and provider functions that follow a pattern-drivenfulfillment model (where specific provider functions can include: aprovider function for calculating a service order; a provider functionfor calculating a technical order; and a provider function for designinga service by selecting and assembling supporting components); andinterfaces (where specific interfaces can include: a service order; anda technical order). Fulfillment solution blueprint 221 is furtherdescribed below in greater detail. Thus, service order deliverycomponent 220 can leverage the domain information models structuredwithin technical catalog 211, and provide a suite of softwareapplications for service fulfillment, architected according tofulfillment solution blueprint 221.

FIG. 3 illustrates a flow diagram of the functionality of a servicedesign and order fulfillment module, according to an embodiment of theinvention. In one embodiment, the functionality of the flow diagram ofFIG. 3, and the functionality of the flow diagrams of FIGS. 9, 13, 20,25, 30, 38, 43, 50, and 56, are each implemented by software stored inmemory or other computer-readable or tangible medium, and executed by aprocessor. In other embodiments, each functionality may be performed byhardware (e.g., through the use of an application specific integratedcircuit (“ASIC”), a programmable gate array (“PGA”), a fieldprogrammable gate array (“FPGA”), etc.), or any combination of hardwareand software.

The flow begins and proceeds to 310. At 310, a technical catalog isdefined that includes one or more items including metadata used by aprovider function of a fulfillment solution. In certain embodiments, thetechnical catalog can be defined by defining one or more entity modelitems including metadata that defines one of: an entity, or one or moreattributes of an entity. In some of these embodiments, defining one ormore entity model items can include defining at least one of: an entityincluding metadata that defines a capability that is provided; arelationship including metadata that defines an association between afirst entity and a second entity; a mapping including metadata thatdefines an association between a first entity, one or more attributes ofthe first entity, or one or more attribute values of the first entity,and a second entity, one or more attributes of the second entity, or oneor more attribute values of the second entity; or an action includingmetadata that defines a pattern of a structured request to perform workon a subject.

In certain embodiments, the technical catalog can further be defined bydefining one or more behavior model items including metadata thatdefines a behavior of an entity. In some of these embodiments, definingone or more behavior model items can include defining at least one of: afulfillment pattern including metadata that defines a set of one or morefulfillment functions and one or more dependencies; a transformationsequence including metadata that defines customizable process logic,where the customizable process logic is structured within one or morestages; or a static process including metadata that defines staticprocess logic.

Further, in certain embodiments, the technical catalog can further bedefined by defining one or more infrastructure model items includingmetadata that defines a fulfillment topology. In some of theseembodiments, defining one or more infrastructure model items can includedefining at least one of: an order specification including metadata thatdefines a structure of an order; a fulfillment function includingmetadata that defines a unit of fulfillment work provided by afulfillment system; or a fulfillment topology including metadata thatdefines a set of one or more fulfillment systems. The flow proceeds to320.

At 320, a fulfillment solution blueprint is defined that includes aplurality of order layers that define a plurality of layers of thefulfillment solution, a plurality of provider functions that are aplurality of components of the fulfillment solution, and a plurality ofinterface contracts defining a plurality of interactions between aplurality of provider functions.

In certain embodiments, the defining the fulfillment solution blueprintcan include: defining a customer order layer configured to orchestrate acustomer order and to transform the customer order into a service order;defining a service order layer configured to orchestrate the serviceorder and to generate a technical order based on the service order; anddefining a technical order layer configured to orchestrate the technicalorder.

Further, in certain embodiments, the defining the fulfillment solutionblueprint can further include defining at least one of: a service ordercalculation provider function configured to transform a customer orderinto a service order; a service order orchestration provider functionconfigured to receive a service order and generate an orchestration planthat fulfills the service order; a service order design and assignprovider function configured to receive a service order and generate aservice instance (including a configuration of resource-facing servicesand/or resources) based on the service order; a technical ordercalculation provider function configured to generate a technical orderbased on a configuration of resource-facing services and/or resourcesbased on a service order; a technical order orchestration providerfunction configured to receive a technical order and generate anorchestration plan that fulfills the technical order; or a technicalorder activation provider function configured to receive a technicalorder and translate the technical order into one or more commandsequences delivered to one or more infrastructure elements.

Further, in certain embodiments, the defining the fulfillment solutionblueprint can further include defining at least one of: a customer orderincluding one or more customer order lines, where each customer orderline includes a product action on a product offering that is based on aproduct specification; a service order including one or more serviceorder lines, where each service order line includes a service action ona customer-facing service that is based on a customer-facing servicespecification; or a technical order including one or more technicalorder lines, where each technical order line includes a technical actionon a resource-facing service that is based on a resource-facing servicespecification, or a resource that is based on a resource specification.The defining the fulfillment solution blueprint can further includedefining at least one service design and order fulfillment systemcomponent to implement at least one provider function of at least oneorder layer of the fulfillment solution blueprint. The flow proceeds to330.

At 330, a fulfillment solution is designed to use at least one item ofthe one or more items of the technical catalog to fulfill an order. Theflow proceeds to 340.

At 340, the fulfillment solution is further designed based on thefulfillment solution blueprint. In certain embodiments, the fulfillmentsolution is defined to include the one or more provider functions of thefulfillment solution blueprint. The flow proceeds to 350.

At 350, the fulfillment solution is generated based on the fulfillmentsolution blueprint using the at least one item of the one or more itemsof the technical catalog. The flow then ends.

Thus, an overall service design and order fulfillment system is providedthat can utilize a technical catalog and a fulfillment solutionblueprint to design services and fulfill service orders. The system canprovide business agility by reducing the time and risk involved indefining a new service or redefining an existing service. The system canalso reduce operational costs and improve customer experience byreducing processing exceptions and providing order status transparency.The system can further provide flexibility in how services may becommercialized, and can allow for a straightforward implementation ofvarious business models through a use of interfaces. The system canfurther reduce a total cost of ownership of a fulfillment solution byenabling consolidation of software, hardware, and skills across multiplelines of products and services.

According to another embodiment, a service design and order fulfillmentsystem can provide a technical catalog, where the technical catalog is adesign for the content, structure, and usage of a metadata catalog,where the technical catalog can feature a design for a content,structure, and usage of a metadata catalog, and where the metadata ofthe technical catalog can configure a behavior of a service design andorder fulfillment system. The metadata of the technical catalog candrive operational behavior following a pattern-driven fulfillment model.The technical catalog can include definitions associated with aspecification, such as an action or a fulfillment pattern.

FIG. 4 illustrates an information model 400 of a technical catalog,according to an embodiment of the invention. A technical catalog is adata store that can be part of a service design and order fulfillmentsystem, and that can store metadata that is utilized by the servicedesign and order fulfillment system. The technical catalog furtherincludes information model 400, where information model 400 defines astructure, content, and pattern of usage of the metadata stored withinthe technical catalog. More specifically, information model 400 formatsthe metadata into one or more items, where an item is a unit ofmetadata. According to the illustrated embodiment, information model 400categories each item as an item of one of the following categories:entity model items 410; behavior model items 420, or infrastructuremodel items 430.

Entity model items 410 are items based on an entity meta-model anchoredon one or more specific entities adapted from an information/data model.More specifically, entity model items 410 are items that includemetadata, where the metadata either defines one or more entities 411, orone or more attributes of entities 411.

Entities 411 are entities that include metadata that defines acapability that is provided by a fulfillment solution. In certainembodiments, entities 411 can include at least one of: a productspecification 412, a customer-facing service specification 413, aresource-facing service specification 414, or a resource specification415. According to the embodiment, product specification 412 includesmetadata that defines a product that is provided by a fulfillmentsolution, customer-facing service specification 413 includes metadatathat defines a customer-facing service that is provided by a fulfillmentsolution, resource-facing service specification 414 includes metadatathat defines a resource-facing service that is provided by a fulfillmentsolution, and resource specification 414 includes metadata that definesa resource that is provided by a fulfillment solution.

Further, in certain embodiments where entity model items 410 include oneor more items whose metadata defines one or more attributes of entities411, the one or more items can include one or more relationships 416,one or more mappings 417, or one or more actions 418. A relationshipincludes metadata that defines an association between a first entity ofentities 411 and a second entity of entities 411. In alternateembodiments, a relationship can include metadata that defines anassociation between a set of one or more entities of entities 411 andanother set of one or more entities of entities 411. A mapping includesmetadata that defines an association between a first entity of entities411, one or more attributes of the first entity of entities 411, or oneor more attribute values of the first entity of entities 411, and asecond entity of entities 411, one or more attributes of the secondentity of entities 411, or one or more attribute values of the secondentity of entities 411, where the association can include atransformation or translation. An action includes metadata that definesa pattern of a structured request to perform work on a subject.

Behavior model items 420 are items that include metadata, where themetadata defines a behavior of an entity (such as an entity of entities411). In certain embodiments, behavior model items 420 can include oneor more fulfillment patterns 421, one or more transformation sequences422, one or more static processes 423, or other logic 424. Eachfulfillment pattern of fulfillment patterns 421 includes metadata thatdefines a set of one or more fulfillment functions and one or moredependencies. Each transformation sequence of transformation sequences422 includes metadata that defines customizable process logic, where thecustomizable process logic is structured within one or more stages. Eachstatic process of static processes 423 includes metadata that definesstatic process logic. Other logic 424 can include metadata that definesany other types of process or programming logic.

Infrastructure model items 430 are items that include metadata, wherethe metadata defines a fulfillment topology. In certain embodiments,infrastructure model items 430 can include one or more orderspecifications 431, one or more fulfillment functions 432, one or morefulfillment topologies 433, or other fulfillment metadata 434. Eachorder specification of order specifications 431 includes metadata thatdefines a structure of an order. Each fulfillment function offulfillment functions 432 includes metadata that defines a unit offulfillment work provided by a fulfillment system. Each fulfillmenttopology of fulfillment topologies 433 includes metadata that defines aset of one or more fulfillment systems, where the fulfillment topologybelongs to one or more fulfillment system types, and where thefulfillment topology includes one or more fulfillment providers, and oneor more fulfillment functions. Other fulfillment metadata 434 caninclude any other types of fulfillment metadata.

According to an embodiment, a technical catalog (such as the technicalcatalog illustrated in FIG. 4) can provide a set of one or more items,where the items can be used as building blocks to drive or tailor abehavior of one or more provider functions of one or more fulfillmentsolutions utilized by a service design and order fulfillment system.Each provider function can vary its behavior based on an executioncontext which may include one or more items within the technicalcatalog. Additionally, changes to one or more items within the technicalcatalog may cause changes to a behavior of one or more providerfunctions. Further, a technical catalog can provide a model for aparticular domain (e.g., GSM, broadband, VPN, etc.). By using items ofthe technical catalog that may be service-domain-specific,domain-agnostic provider functions can tailor their behavior to matchfulfillment requirements of a variety of service domains. Hence, onefulfillment solution is capable of support of any service domain. Thus,durability and stability can be added to an overall service design andorder fulfillment system.

FIG. 5 illustrates a service design 500 that includes an example set ofentity model items of a technical catalog, according to an embodiment ofthe invention. By adding the set of entity model items to service design500, a fulfillment solution generated from service design 500 can beenable to support new entities.

According to the embodiment, service design 500 includes productspecifications 510, 511, and 512. Product specification 510 is a productspecification for a broadband product. Product specification 511 is aproduct specification for a broadband bandwidth product. Productspecification 512 is a product specification for an email serviceproduct. By designing service design 500 to include productspecifications 510, 511, and 512, the subjects of a fulfillment solutiongenerated from service design 500 can include a broadband product, abroadband bandwidth product, and an email service product.

Service design 500 further includes customer-facing servicespecifications 520 and 521. Customer-facing service specification 520 isa customer-facing service specification for a broadband internet accesscustomer-facing service. Customer-facing service specification 521 is acustomer-facing service specification for an email customer-facingservice. By designing service design 500 to include customer-facingservice specifications 520 and 521, the subjects of a fulfillmentsolution generated from service design 500 can include a broadbandinternet access customer-facing service and an email customer-facingservice.

Service design 500 also includes resource-facing service specifications530 and 531. Resource-facing service specification 530 is aresource-facing service specification for a DSL resource-facing service.Resource-facing service specification 531 is a resource-facing servicespecification for an email resource-facing service. By designing servicedesign 500 to include resource-facing service specifications 530 and531, the subjects of a fulfillment solution generated from servicedesign 500 can include a DSL resource-facing service and an emailresource-facing service.

Service design 500 further includes resource specifications 532, 533,534, and 535. Resource specification 532 is a resource specification fora DSL CPE resource. Resource specification 533 is a resourcespecification for an asymmetrical digital subscriber line (“ADSL”) portresource. Resource specification 534 is a resource specification for alocal loop resource. Resource specification 535 is a resourcespecification for an email account resource. By designing service design500 to include resource specifications 532, 533, 534, and 535, thesubjects of a service that is generated from service design 500 caninclude a DSL CPE resource, an ADSL port resource, a local loopresource, and an email account resource.

Service design 500 further includes relationships 540, 541, 542, 543,544, 545, and 546. Each relationship of relationships 540, 541, 542,543, 544, 545, and 546 can be a type of relationship selected from aplurality of relationship types. Such relationship types can include: acorrelation relationship (e.g., a relationship between a productspecification and a customer-facing service specification, or arelationship between a customer-facing service specification and aresource-facing service specification), a composite relationship (e.g.,a relationship between a resource-facing service specification and aresource specification), or a fulfillment target relationship thatmatches an entity to a fulfillment target where the entity is deliveredfrom. In the illustrated embodiment, relationships 540, 541, 542, 543,and 544 are examples of a correlation relationship, and relationships545 and 546 are examples of a composite relationship.

Relationship 540 is a relationship that defines an association betweenproduct specification 510 and customer-facing service specification 520.Relationship 541 is a relationship that defines an association betweenproduct specification 511 and customer-facing service specification 520.Relationship 542 is a relationship that defines an association betweenproduct specification 512 and customer-facing service specification 521.By designing service design 500 to include relationships 540, 541, and542, a fulfillment solution generated from service design 500 canassociate both a broadband product and a broadband bandwidth productwith a broadband internet access customer-facing service, and canfurther associate an email service product with an email customer-facingservice.

Further, relationship 543 is a relationship that defines an associationbetween customer-facing service specification 520 and resource-facingservice specification 530. Relationship 544 is a relationship thatdefines an association between customer-facing service specification 521and resource-facing service specification 531. By designing servicedesign 500 to include relationships 543 and 544, a fulfillment solutiongenerated from service design 500 can associate a broadband internetaccess customer-facing service with a DSL resource-facing service, andcan also associate an email customer-facing service with an emailresource-facing service.

Further, relationship 545 is a relationship that defines an associationbetween resource-facing service specification 530 and resources 532,533, and 534. Relationship 546 is a relationship that defines anassociation between resource-facing service specification 531 andresource 535. By designing service design 500 include relationships 545and 546, a fulfillment solution generated from service design 500 canassociate a DSL resource-facing service with a DSL CPE resource, an ADSLport resource, and a local loop resource, and can also associate anemail resource-facing service with an email account resource.

Service design 500 also includes mappings 550, 551, and 552. Mapping 550is a mapping that defines an association between product specification510, one or more attributes of product specification 510, or one or moreattribute values of product specification 510, and customer facingservice specification 520, one or more attributes of customer facingservice specification 520, or one or more attribute values of customerfacing service specification 520. Mapping 551 is a mapping that definesan association between product specification 511, one or more attributesof product specification 511, or one or more attribute values of productspecification, and customer-facing service specification 520, one ormore attributes of customer-facing service specification 520, or one ormore attribute values of customer-facing service specification 520.Mapping 552 is a mapping that defines an association between productspecification 512, one or more attributes of product specification 512,or one or more attribute values of product specification 512, andcustomer-facing service specification 521, one or more attributes ofcustomer-facing service specification 521, or one or more attributevalues of customer-facing service specification 521. By designingservice design 500 to include mappings 550, 551, and 552, a fulfillmentsolution generated from service design 500 can associate one or moreattributes of both a broadband product and a broadband bandwidth productwith one or more attributes of a broadband internet accesscustomer-facing service, and can further associate one or moreattributes of an email service product with one or more attributes of anemail customer-facing service.

FIG. 6 illustrates a service design 500 that includes an example set ofentity model items and behavior model items of a technical catalog,according to an embodiment of the invention. By adding the set of entitymodel items and behavior model items to service design 500, logic of afulfillment solution generated from service design 500 can be furthercustomized.

According to the embodiment, service design 500 includes actions 610,611, 612, and 613. Action 610 defines a pattern of a structured requestto perform work on a customer-facing service that is based oncustomer-facing service specification 520. Action 611 defines a patternof a structured request to perform work on a customer-facing servicethat is based on customer-facing service specification 521. Action 612defines a pattern of a structured request to perform work on aresource-facing service that is based on resource-facing servicespecification 530. Action 613 defines a pattern of a structured requestto perform work on a resource-facing service that is based onresource-facing service specification 531. By designing service design500 to include actions 610, 611, 612, and 613, a fulfillment solutiongenerated from service design 500 can perform an action on a broadbandinternet access customer-facing service, an email customer-facingservice, a DSL resource-facing service, and an email resource-facingservice.

Service design 500 further includes fulfillment patterns 620 and 621.Fulfillment pattern 620 defines a set of one or more fulfillmentfunctions and one or more dependencies for customer-facing servicespecification 520. Fulfillment pattern 621 defines a set of one or morefulfillment functions and one or more dependencies for customer-facingservice specification 521. By designing service design 500 to includefulfillment patterns 620 and 621, a fulfillment solution generated fromservice design 500 can apply a fulfillment pattern to a broadbandinternet access customer-facing service and an email customer-facingservice.

FIG. 7 illustrates a service design 500 that includes another exampleset of entity model items and behavior model items of a technicalcatalog, according to an embodiment of the invention. By adding theadditional set of entity model items and behavior model items to servicedesign 500, logic of a fulfillment solution generated from servicedesign 500 can be further customized.

According to the embodiment, service design 500 includes resourcespecifications 710, 711, 712, 713, and 714. Resource specifications 710,711, 712, 713, and 714 further represent fulfillment target types.Resource specification 710 is a resource specification for a CPEmanagement system resource. Resource specification 711 is a resourcespecification for a warehouse resource. Resource specification 712 is aresource specification for an access node resource. Resourcespecification 713 is a resource specification for a loop providerresource. Resource specification 714 is a resource specification for anemail server resource. By designing service design 500 to includeresource specifications 710, 711, 712, 713, and 714, the targets of aservice that is generated from service design 500 can include a CPEmanagement system resource, a warehouse resource, an access noderesource, a loop provider resource, and an email server resource.

Service design 500 further includes relationships 720, 721, 722, and723. Relationships 720, 721, 722, and 723 are of a referential natureand identify a target for any action on a subject. Each relationship ofrelationships 720, 721, 722, and 733 can be a type of relationshipselected from a plurality of relationship types. Such relationship typescan include: a correlation relationship (e.g., a relationship between aproduct specification and a customer-facing service specification or arelationship between a customer-facing service specification and aresource-facing service specification), a composite relationship (e.g.,a relationship between a resource-facing service specification and aresource specification), or a fulfillment target relationship thatmatches an entity to a fulfillment target where the entity is deliveredfrom. In the illustrated embodiments, relationships 720, 721, 722, and723 are each examples of a fulfillment target relationship.

Relationship 720 is a relationship that defines an association betweenresource specification 532 and resource specifications 710 and 711.Relationship 721 is a relationship that defines an association betweenresource-facing service specification 530 and resource specification712. Relationship 722 is a relationship that defines an associationbetween resource specification 534 and resource specification 713.Relationship 723 is a relationship that defines an association betweenresource-facing service specification 531 and resource 714. By designingservice design 500 to include relationships 720, 721, 722, and 723, afulfillment solution generated from service design 500 can associate aDSL CPE resource with both a CPE management system resource and awarehouse resource, can associate a DSL resource-facing service with anaccess node resource, can associate a local loop resource with a loopprovider resource, and can further associate an email resource-facingservice with an email server resource.

Service design 500 further includes actions 730, 731, 732, 733, and 734.Action 730 defines a pattern of a structured request to perform work ona resource that is based on resource specification 710. Action 731defines a pattern of a structured request to perform work on a resourcethat is based on resource specification 711. Action 732 defines apattern of a structured request to perform work on a resource that isbased on resource specification 712. Action 733 defines a pattern of astructured request to perform work on a resource that is based onresource specification 713. Action 734 defines a pattern of a structuredrequest to perform work on a resource that is based on resourcespecification 714. By designing service design 500 to include actions730, 731, 732, 733, and 734, a fulfillment solution generated fromservice design 500 can perform an action on a CPE management systemresource, a warehouse resource, an access node resource, a loop providerresource, and an email server resource. According to the embodiment,action 730 is performed on resource specification 532 as the subject anddirected to resource specification 710 as the target, action 731 isperformed on resource specification 532 as the subject and directed toresource specification 711 as the target, action 732 is performed onresource-facing service specification 530 as the subject and directed toresource specification 712 as the target, action 733 is performed onresource specification 534 as the subject and directed to resourcespecification 713 as the target, and action 734 is performed onresource-facing service specification 531 as the subject and directed toresource specification 714 as the target.

Service design 500 further includes fulfillment patterns 740, 741, 742,and 743. Fulfillment pattern 740 defines a set of one or morefulfillment functions and one or more dependencies for resourcespecification 720. Fulfillment pattern 741 defines a set of one or morefulfillment functions and one or more dependencies for resource-facingservice specification 530. Fulfillment pattern 742 defines a set of oneor more fulfillment functions and one or more dependencies for resourcespecification 534. Fulfillment pattern 743 defines a set of one or morefulfillment functions and one or more dependencies for resource-facingservice specification 531. In certain embodiments, fulfillment patterns740, 741, 742, and 743 are unique fulfillment patterns. In otheralternate embodiments, one or more of fulfillment patterns 740, 741,742, and 743 are identical to each other. By designing service design500 to include fulfillment patterns 740, 741, 742, and 743, afulfillment solution generated from service design 500 can apply afulfillment pattern to a DSL CPE resource, a DSL resource-facingservice, a local loop resource, and an email resource-facing service.

FIG. 8 illustrates an example set of infrastructure model items of atechnical catalog, according to an embodiment of the invention. Byadding the set of infrastructure model items to service design 500,logic of a service that is generated from service design 500 can befurther customized.

According to the embodiment, service design 500 includes orderspecifications 810 and 811. Order specification 810 is a service orderspecification that defines a structure of a service order. Orderspecification 811 is a technical order specification that defines astructure of a technical order. By designing service design 500 toinclude order specifications 810 and 811, a fulfillment solutiongenerated from service design 500 can perform functionality on a serviceorder as well as a technical order.

Service design 500 further includes fulfillment functions 820, 821, 822,and 823. Fulfillment function 820 is a design and assign (i.e. “Designand Assign”) fulfillment function that can generate a service instancefrom a service order. Fulfillment function 821 is an order activation(i.e., “Activate Order”) fulfillment function that can perform workassociated with activating a technical order. Fulfillment function 822is an order shipment (i.e., “Ship Order”) function that can perform workassociated with shipping a technical order. Fulfillment function 823 isan order install (i.e., “Install Order”) fulfillment function that canperform work associated with installing a technical order. By designingservice design 500 to include fulfillment functions 820, 821, 822, and823, a fulfillment solution generated from service design 500 cangenerate a service instance from a service order, activate a technicalorder, ship a technical order, and install a technical order.

Service design 500 further includes fulfillment topologies 830 and 840.Fulfillment topology 830 is a set of fulfillment systems associated withorder specification 810. More specifically, fulfillment topology 830includes a fulfillment system that belongs to fulfillment system type831, and that includes fulfillment function 820, and fulfillmentproviders 632 and 633. Fulfillment topology 840 is a set of fulfillmentsystems associated with order specification 820. More specifically,fulfillment topology 840 includes: a fulfillment system that belongs tofulfillment system type 841, and that includes fulfillment function 821,and fulfillment provider 844; a fulfillment system that belongs tofulfillment system type 842, and that includes fulfillment function 822,and fulfillment provider 845; and a fulfillment system that belongs tofulfillment system type 843, and that includes fulfillment function 823,and fulfillment provider 846. By designing service design 500 to includefulfillment topologies 830 and 840, a fulfillment solution generatedfrom service design 500 can utilize different fulfillment topologies forfulfilling a service order and a technical order.

FIG. 9 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention. The flow begins and proceeds to 910. At910, one or more entity model items are defined. Each entity model itemincludes metadata that defines one of: an entity; or one or moreattributes of an entity. The metadata can be used by a fulfillmentsolution, and each entity model item can be used by the fulfillmentsolution to fulfill an order. In certain embodiments, at least one ofthe following is defined: an entity including metadata that that definesa capability that is provided; a relationship including metadata thatdefines an association between a first entity and a second entity; amapping including metadata that defines an association between a firstentity, one or more attributes of the first entity, or one or moreattribute values of the first entity, and a second entity, one or moreattributes of the second entity, or one or more attribute values of thesecond entity; or an action including metadata that defines a pattern ofa structured request to perform work on a subject. In embodiments wherean entity is defined, at least one of the following is defined: aproduct specification including metadata that defines a product that isprovided; a customer-facing service specification including metadatathat defines a customer-facing service that is provided; aresource-facing service specification including metadata that defines aresource-facing service that is provided; or a resource specificationincluding metadata that defines a resource that is provided. The flowthen proceeds to 920.

At 920, one or more behavior model items are defined. Each behaviormodel item includes metadata that defines a behavior of an entity. Themetadata can be used by a fulfillment solution, and each behavior modelitem can be used by the fulfillment solution to fulfill an order. Incertain embodiments, at least one of the following is defined: afulfillment pattern including metadata that defines a set of one or morefulfillment functions and one or more dependencies; a transformationsequence including metadata that defines customizable process logic,where the customized process logic is structured within one or morestages; or a static process including metadata that defines staticprocess logic. The flow then proceeds to 930.

At 930, one or more infrastructure model items are defined. Eachinfrastructure model item includes metadata that defines a fulfillmenttopology. The metadata can be used by a fulfillment solution, and eachinfrastructure model item can be used by the fulfillment solution tofulfill an order. In certain embodiments, at least one of the followingis defined: an order specification including metadata that describes astructure of an order; a fulfillment function including metadata thatdefines a unit of fulfillment work provided by a fulfillment system; ora fulfillment topology including metadata that defines a set offulfillment systems. The flow then proceeds to 940.

At 940, the one or more items (i.e., the one or more entity model items,the one or more behavior model items, and the one or more infrastructuremodel items), are stored within a technical catalog. The technicalcatalog is a data store that stores metadata. The technical catalogfurther defines a structure of the one or more items. The flow thenproceeds to 950.

At 950, a fulfillment solution is designed to use at least one item ofthe one or more items (i.e., the one or more entity model items, the oneor more behavior model items, and the one or more infrastructure modelitems) to fulfill an order. In certain embodiments, the fulfillmentsolution is designed to include one or more provider functions, whereeach provider function uses at least one item of the one or more items.In some of these embodiments, the provider function includes a logicalcomponent of the fulfillment solution configured to provide acapability, and the provider function is configured to act upon adefined input and generate a defined output. Further, in certainembodiments, the fulfillment solution includes a metadata-drivenexecutable process that fulfills an order. By fulfilling an order, thefulfillment solution can generate an orchestration plan that fulfillsthe order. In some of these embodiments, the order is an order forcommunication services. The flow then proceeds to 960.

At 960, the fulfillment solution is generated using the at least oneitem of the one or more items (i.e., the one or more entity model items,the one or more behavior model items, and the one or more infrastructuremodel items). The flow then ends. In alternate embodiments, the flow canproceed according to an alternate sequence that is different from thesequence illustrated in FIG. 9.

Thus, in one embodiment, a service design and order fulfillment systemcan provide a technical catalog that provides a particular structure,content, and usage. Aspects of the business that are relevant to afulfillment system can be captured in the technical catalog, in a formthat is coherent, comprehensive, and meaningful to business users.Further, the technical catalog can utilize patterns that enablescalability of behavior variations, based on compact and manageable setsof metadata. This can result in a versatile fulfillment system. Thetechnical catalog can be structured and used in ways that enable rapidadaptation of a service fulfillment solution to business changes andopportunities. The technical catalog can facilitate rapid communicationbetween a technical community and a commercial community, using a commonmodel and vocabulary to describe service behavior in a servicefulfillment context. An information model structured in this way can bestraightforward to analyze and use without requiring significanttechnical knowledge of specific operational support system software.Changes to such an information model can be transparently correlated tobusiness impacts, which can enable adaption work to be localized andplanned. Further, due to localization of changes to the technicalcatalog, reliable and efficient fulfillment operations can bemaintained, thus minimizing the possibility of change-induced errorsresulting in the service fulfillment solution.

According to another embodiment, a service design and order fulfillmentsystem can provide a fulfillment solution blueprint, where thefulfillment solution blueprint is an organizational schema for theservice design and order fulfillment system that can support a widerange of services, such as communications/information services, withminimal reconfiguration. The fulfillment solution blueprint can define aset of contract interfaces and provider functions that are allindependent of any service domain, allowing a single service design andorder fulfillment system to support multiple domains, and for newdomains to be easily introduced. The fulfillment solution blueprint canfeature: (a) a separation between a commercial layer and a servicelayer; (b) a separation between a service layer and a technical layer;and (c) an orchestration decoupled from a fulfillment topology. Thefulfillment solution blueprint can be defined in terms of: (a) processesand provider functions that follow a pattern-driven fulfillment model,where specific provider functions can include: (1) a provider functionfor calculating a service order; (2) a provider function for calculatinga technical order; and (3) a provider function for designing a serviceby selecting and assembling supporting components; and (b) interfaces,where specific interfaces can include (1) a service order; and (2) atechnical order.

Further, according to the embodiment, a fulfillment solution blueprintcan be an organizational schema for a fulfillment solution that canprovide a logical ordering of provider functions within a logicalordering of order layers. For example, a fulfillment solution mayreceive a customer request via an order, where the customer request isto perform an action on an infrastructure or network element. Thefulfillment solution blueprint can provide an organizational breakdownof a fulfillment solution, where the fulfillment solution is broken downinto a plurality of order layers, and each order layer is broken downinto a plurality of provider functions. The fulfillment solutionblueprint can be used by a service design and order fulfillment solutionto design and generate a fulfillment solution that can transform theorder, through various order layers, into an action on an infrastructureor network element. Thus, the fulfillment solution blueprint is adocumented expression of a partitioning of fulfillment functionalityinto one or more order layers, where each order layer is partitionedinto one or more provider functions.

FIG. 10 illustrates an example fulfillment solution blueprint 1000,according to an embodiment of the invention. According to theembodiment, fulfillment solution blueprint 1000 includes three orderlayers: customer order layer (i.e., customer layer) 1010, service orderlayer (i.e., service layer) 1011, and technical order layer (i.e.,technical layer) 1012. Each order layer defines a layer of an overallfulfillment solution, and each order layer is configured to fulfill atype of order among multiple provider functions, fulfillment systemtypes, and fulfillment providers. By fulfilling a type of order, eachorder layer can generate an orchestration plan that fulfills the type oforder. More specifically, customer layer 1010 is configured to fulfill acustomer order, which can involve transforming a customer order into aservice order. Service layer 1011 is configured to fulfill a serviceorder, which can involve generating a technical order based on a serviceinstance (including a configuration of resource-facing services and/orresources). Technical layer 1012 is configured to fulfill a technicalorder. The number and layout of order layers for fulfillment solutionblueprint 1000 is an example number and layout of order layers accordingto an example embodiment. In alternate embodiments, a fulfillmentsolution blueprint can have any number and layout of order layers.

Further, customer layer 1010 is decoupled from service layer 1011, andservice layer 1011 is decoupled from technical layer 1012. In otherwords, the three order layers are separated and ordered, where customerlayer 1010 is the first layer of the fulfillment solution blueprint,service layer 1011 is the second layer of the fulfillment solutionblueprint, and technical order layer 1012 is the third layer of thefulfillment solution blueprint. Decoupling of a customer layer from aservice layer is further described below in greater detail. Decouplingof a service layer from a technical layer is further described in U.S.Patent Application Publication No. 2012/0150676, U.S. Patent ApplicationPublication No. 2012/0150583, U.S. Patent Application Publication No.2012/0150692, U.S. Patent Application Publication No. 2012/0150582, andU.S. Patent Application Publication No. 2012/0150693. Additionally,customer layer 1010, service layer 1011, and technical layer 1012, areeach decoupled from a specific fulfillment topology, where the specificfulfillment topology is utilized to fulfill the respective orderaccording to an orchestration plan generated by the respective orderlayer. Decoupling of a fulfillment flow, such as an orchestration plan,from a fulfillment topology is further described in U.S. PatentApplication Publication No. 2012/0150676, U.S. Patent ApplicationPublication No. 2012/0150583, U.S. Patent Application Publication No.2012/0150692, U.S. Patent Application Publication No. 2012/0150582, andU.S. Patent Application Publication No. 2012/0150693.

According to the embodiment, fulfillment solution blueprint 1000includes six service design and order fulfillment system components: aCRM component 1020, a COM component 1021, a SOM component 1022, a SRMcomponent 1023, a TOM component 1024, and an activation component 1025.Each service design and order fulfillment system component can beassigned to an order layer and defined to implement one or more providerfunctions and/or one or more interface contracts.

In the illustrated embodiment, CRM component 1020 can capture one ormore customer orders. COM component 1021 can receive one or morecustomer orders and orchestrate them among various fulfillment systemcomponents, such as a billing component, a service fulfillmentcomponent, a supply chain management component, and a workforcemanagement component. COM component 1021 can further transform the oneor more customer orders into one or more service orders. SOM component1022 can receive one or more service orders from COM component 1021, andorchestrate the one or more service orders among SRM component 1023 andTOM component 1024. SOM component 1022 can optionally pre-process acustomer order to derive a service order. SOM component 1022 can furthergenerate one or more technical orders based on the one or more serviceorders. SRM component 1023 can receive one or more service order linesof one or more service orders and perform a service order design andassign function, as well as a technical order calculation function. TOMcomponent 1024 can receive one or more technical orders from SOMcomponent 1022, and orchestrate the one or more technical orders amongvarious service design and order fulfillment system components, such asan activation component, a supply chain management component, and aworkforce management component. Activation component 1025 can receiveone or more technical order lines and perform a technical orderactivation fulfillment function.

Fulfillment solution blueprint 1000 further includes eleven providerfunctions: a customer order capture provider function 1030, a customerorder orchestration provider function 1031, a service order calculationprovider function 1032 (for customer layer 1010), a customer orderprovisioning provider function 1033, a service order calculationprovider function 1034 (for service layer 1011), a service orderorchestration provider function 1035, a service order design and assignprovider function 1036, a technical order calculation provider function1037, a technical order orchestration provider function 1038, atechnical order activation orchestration provider function 1039, anactivation command calculation provider function 1040, and an activationcommand fulfillment provider function 1041. Each provider function is adurable and domain-agnostic provider function, which can interact withanother provider function according to a specific topologicalconfiguration via stable interfaces. Further, each provider function isa component of an overall fulfillment solution, where each providerfunction is configured to provide a capability and is configured to actupon a defined input and generate a defined output. In certainembodiments, each provider function includes one or more items of atechnical catalog, wherein each item defines metadata for the providerfunction. Also, in certain embodiments, each provider function can becreated based on a dynamic pattern-driven fulfillment model.

In the illustrated embodiment, service order orchestration providerfunction 1035 is a provider function configured to generate anorchestration plan that fulfills the service order. Service orderorchestration provider function 1035 is further capable of invoking, asneeded, service order calculation provider function 1034, where serviceorder calculation provider function 1034 is a provider functionconfigured to transform a customer order into a service order. Serviceorder design and assign provider function 1036 is a provider functionconfigured to receive a service order and generate a service instance(including a configuration of resource-facing services and/or resources)based on the service order. Technical order calculation providerfunction 1037 is a provider function configured to generate a technicalorder based on a change to a configuration of resource-facing servicesand/or resources. Technical order orchestration provider function 1038is a provider function configured to receive a technical order andgenerate an orchestration plan that fulfills the technical order.Technical order activation orchestration provider function 1039 is aprovider function configured to receive a technical order and translatethe technical order into one or more command sequences delivered to oneor more infrastructure elements.

Regarding customer layer 1010, CRM component 1020 and customer ordercapture provider function 1030 can be assigned to customer layer 1010,where CRM component 1020 can be defined to implement customer ordercapture provider function 1030. COM component 1030, customer orderorchestration provider function 1031, service order calculation providerfunction 1032, and customer order provisioning provider function 1033can also be assigned to customer layer 1010, where COM component 1021can be defined to implement customer order orchestration providerfunction 1031, service order calculation provider function 1032, andcustomer order provisioning provider function 1033.

Regarding service layer 1011, SOM component 1022, service ordercalculation provider function 1034, and service order orchestrationprovider function 1035 can be assigned to service layer 1011, where SOMcomponent 1022 can be defined to implement service order calculationprovider function 1034, and service order orchestration providerfunction 1035. SRM component 1023, service order design and assignprovider function 1036, and technical order calculation providerfunction 1037 can also be assigned to service layer 1011, where SRMcomponent 1023 can be defined to implement service order design andassign provider function 1036, and technical order calculation providerfunction 1037.

Regarding technical layer 1012, TOM component 1024 and technical orderorchestration provider function 1038 can be assigned to technical layer1012, where TOM component 1024 can be defined to implement technicalorder orchestration provider function 1038. Activation component 1025,technical order activation orchestration provider function 1039,activation command calculation provider function 1040, and activationcommand fulfillment provider function 1041 can also be assigned totechnical layer 1012, where activation component 1025 can be defined toimplement technical order activation orchestration provider function1039, activation command calculation provider function 1040, andactivation command fulfillment provider function 1041.

The number and layout of service design and order fulfillment systemcomponents for fulfillment solution blueprint 1000 is an example numberand layout of service design and order fulfillment system componentsaccording to an example embodiment. In alternate embodiments, afulfillment solution blueprint can have any number of number and layoutof service design and order fulfillment system components. Similarly,the number and layout of provider functions for fulfillment solutionblueprint 1000 is an example number and layout of provider functionsaccording to an example embodiment. In alternate embodiments, afulfillment solution blueprint can have any number and layout ofprovider functions.

Fulfillment solution blueprint 1000 further includes twelve interfacecontracts: customer orders 1040, 1041, 1042, 1043, and 1045, serviceorders 1044, 1046, and 1048, and technical orders 1047, 1049, 1050, and1051. Each interface contract defines an interaction between twoprovider functions, where each interface contract defines either aninput or an output of a provider function. Each interface contract canalso define an interaction between two order layers, and can use apattern that is independent of specific products or services. Further, acustomer order is an order that includes one or more product offeringorder lines. A service order is an order that includes one or morecustomer-facing service order lines. A technical order is an order thatincludes one or more resource-facing service order lines or one or moreresource order lines. Further, fulfillment solution blueprint 1000allows for orders to be input into any layer without necessarily goingthrough prior order layers, provided that the order adheres to theinterface contract.

In the illustrated embodiment, customer order 1040 is an input tocustomer order capture provider function 1030. Customer order 1041 is anoutput of customer order capture provider function 1030, and an input tocustomer order orchestration provider function 1031. Customer order 1042is an input to, and an output of, customer order provisioning providerfunction 1033. Customer order 1043 and service order 1044 are each aninput to service order orchestration provider function 1035. Customerorder 1045, service order 1046, and technical order 1047 are each anoutput of service order orchestration provider function 1035. Serviceorders 1048 and 1049 are an input to, and an output of, both serviceorder design and assign provider function 1036, technical ordercalculation provider function 1037. Technical order 1050 is an output ofservice order orchestration provider function 1035, and an input totechnical order orchestration provider function 1038. Technical order isan output of technical order orchestration provider function 1038, andan input to technical order activation orchestration provider function1039.

FIG. 11 illustrates an example definition of order layers and topologyfor a fulfillment solution blueprint 1100, according to an embodiment ofthe invention. According to the embodiment, fulfillment solutionblueprint 1100 includes customer order layer (i.e., customer layer)1110, service order layer (i.e., service layer) 1111, and technicalorder layer (i.e., technical layer) 1112. Customer layer 1110 is similarto customer layer 1010 of FIG. 10, service layer 1111 is similar toservice layer 1011 of FIG. 10, and technical layer 1112 is similar totechnical layer 1012 of FIG. 10.

According to the embodiment, customer layer 1110 includes COM component1121. COM component 1121 is similar to COM component 1021 of FIG. 10.Further, according to the topology defined for fulfillment solutionblueprint 1100, COM component 1121 can produce an output and can sentthe output to either fulfillment solution 1120 or fulfillment solution1140. Fulfillment solution 1120 and fulfillment solution 1140 are each acollection of provider functions, service design and order fulfillmentcomponents, and contract interfaces that collectively comprise acomponent of an overall fulfillment solution. Further, each providerfunction, service design and order fulfillment component, and contractinterface, can be assigned to either service layer 1111 or technicallayer 1112. The specifics of fulfillment solution 1120 are now describedin greater detail. The specifics of fulfillment solution 1140 are notdescribed in greater detail, but fulfillment solution 1140 isillustrated in FIG. 11 to highlight that fulfillment solution 1140 isdistinct from fulfillment solution 1120, and COM component 1121 can bedesigned to send an output to either fulfillment solution 1120 orfulfillment solution 1140.

According to the embodiment, fulfillment solution 1120 includes SOMcomponent 1122, SRM components 1123 and 1124, TOM component 1125, WFMcomponents 1126 and 1127, activation components 1128 and 1129, and SCMcomponents 1130 and 1131. SOM component 1122 and SRM components 1123 and1124 are assigned to service layer 1111. TOM component 1125, WFMcomponents 1126 and 1127, activation components 1128 and 1129, and SCMcomponents 1130 and 1131 are assigned to technical layer 1112. Further,SOM component 1122 is designed to send an output to SRM components 1123and 1124, and to TOM component 1125. TOM component 1125 is also designedto send an output to WFM components 1126 and 1127, activation components1128 and 1129, and SCM components 1130 and 1131.

FIG. 12 illustrates an example definition of provider functions andcontract interfaces for a fulfillment solution blueprint 1100, accordingto an embodiment of the invention. According to the embodiment,fulfillment solution 1120 includes a service order calculation providerfunction 1205 which can optionally pre-process a customer order toderive a service order. Service order calculation provider function 1205is assigned to service layer 1111, and SOM component 1122 is defined toimplement service order calculation provider function 1205. Fulfillmentsolution 1120 further includes a service order orchestration providerfunction 1210 which can generate an orchestration plan that fulfills theservice order. Service order orchestration provider function 1210 isassigned to service layer 1111, and SOM component 1122 is defined toimplement service order orchestration provider function 1210.Fulfillment solution 1120 further includes a service order design andassign provider function 1220, which can receive a service order andgenerate a service instance (including a configuration ofresource-facing services and/or resources) based on the service order,and a technical order calculation provider function 1230, which cangenerate a technical order based on a change to a configuration ofresource-facing services and/or resources. Service order design andassign provider function 1220 and technical order calculation providerfunction 1230 are assigned to service layer 1111, and SRM components1123 and 1124 are defined to implement service order design and assignprovider function 1220 and technical order calculation provider function1230. Fulfillment solution 1120 further includes a technical orderorchestration provider function 1240, which can receive a technicalorder and generate an orchestration plan that fulfills the technicalorder. Technical order orchestration provider function 1240 is assignedto technical layer 1112, and TOM component 1125 is defined to implementtechnical order orchestration provider function 1240. Fulfillmentsolution 1120 further includes a technical order activation providerfunction 1250, which can receive a technical order and translate thetechnical order into one or more command sequences delivered to one ormore infrastructure elements. Technical order activation providerfunction 1250 is assigned to technical layer 1112, and activationcomponents 1128 and 1128 are defined to implement technical orderactivation provider function 1250. Fulfillment solution 1120 furtherincludes a technical order installation provider function 1260, whichcan implement an installation command sequence. Technical orderinstallation provider function 1260 is assigned to technical layer 1112,and WFM components 1126 and 1127 are defined to implement technicalorder installation provider function 1260. Fulfillment solution 1120further includes a technical order shipping provider function 1270,which can implement a shipping command sequence. Technical ordershipping provider function 1270 is assigned to technical layer 1112, andSCM components 1130 and 1131 are defined to implement technical ordershipping provider function 1270.

Also according to the embodiment, fulfillment solution 1120 includesservice order 1250 and technical order 1260, where service order 1250and technical order 1250 are each type of a contract interface. Serviceorder 1250 is assigned to provider functions 1210, where service order1250 is defined as an input to provider functions 1210. Thus, serviceorder 1250 structures an interaction between customer layer 1110 andservice layer 1111. Further, technical order 1260 is assigned toprovider functions 1230 and provider functions 1240, where technicalorder 1260 is defined as an output of provider functions 1230 anddefined as an input to provider functions 1240. Thus, technical order1260 structures an interaction between service layer 1111 and technicallayer 1112.

FIG. 13 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention. The flow begins and proceeds to 1310. At1310, a plurality of order layers is defined for a fulfillment solutionblueprint. Each order layer defines a layer of a fulfillment solution,and the plurality of order layers are ordered within the fulfillmentsolution blueprint. In certain embodiments, the fulfillment solutionblueprint is an organizational schema of the fulfillment solution.Further, in certain embodiments, the fulfillment solution is ametadata-driven executable process that fulfills an order. In some ofthese embodiments, the order is an order for communication services.

In certain embodiments, in defining a plurality of order layers, acustomer order layer can be defined for the fulfillment solutionblueprint, where the customer order layer is configured to orchestrate acustomer order and to transform the customer order into a service order.A service order layer can also be defined for the fulfillment solutionblueprint, where the service order layer is configured to orchestratethe service order and to generate a technical order based on the serviceorder. A technical order layer can also be defined for the fulfillmentsolution blueprint, where the technical order layer is configured toorchestrate the technical order. The flow then proceeds to 1320.

At 1320, a plurality of provider functions is defined for a fulfillmentsolution blueprint. Each provider function is a component of thefulfillment solution that is configured to provide a capability, andeach provider function is configured to act upon a defined input andgenerate a defined output. In certain embodiments, each providerfunction includes one or more items of a technical catalog, where eachitem defines metadata for the provider function.

In certain embodiments, in defining a plurality of provider functions, aservice order calculation provider function can be defined that isconfigured to transform a customer order into a service order. A serviceorder orchestration provider function can also be defined that isconfigured to receive a service order and generate an orchestration planthat fulfills the service order. A service order design and assignprovider function can also be defined that is configured to receive aservice order and generate a service instance (including a configurationof resource-facing services and/or resources) based on the serviceorder. A technical order calculation provider function can also bedefined that is configured to generate a technical order based on aconfiguration of resource-facing services and/or resources. A technicalorder orchestration provider function can also be defined that isconfigured to receive a technical order and generate an orchestrationplan that fulfills the technical order. A technical order activationprovider function can also be defined that is configured to receive atechnical order and translate the technical order into one or morecommand sequences delivered to one or more infrastructure elements. Theflow then proceeds to 1330.

At 1330, each provider function is assigned to at least one order layer.Each provider function can define a component of the fulfillmentsolution. Further, the plurality of provider functions are orderedwithin the fulfillment solution blueprint. The flow then proceeds to1340.

At 1340, a plurality of interface contracts is defined for thefulfillment solution blueprint. Each interface contract defines aninteraction between two provider functions. Further, each interfacecontract defines either an input or an output of a provider function. Incertain embodiments, in defining a plurality of interface contracts, acustomer order can be defined that includes one or more customer orderlines, where each customer order line includes a product action and aproduct offering based on a product specification. A service order canalso be defined that includes one or more service order lines, whereeach service order line includes a service action and a customer-facingservice based on a customer-facing service specification. A technicalorder can also be defined that includes one or more technical orderlines, where each technical order line includes a technical action and aresource-facing service based on a resource-facing service specificationor a resource based on a resource specification. The flow then proceedsto 1350.

At 1350, each interface contract is assigned to at least one providerfunction. Each interface contract defines an interaction of thefulfillment solution. Further, the plurality of interface contracts areordered within the fulfillment solution blueprint. The flow thenproceeds to 1360.

At 1360, at least one service design and order fulfillment systemcomponent is defined to implement at least one provider function of atleast one order layer of the fulfillment solution blueprint. The flowthen proceeds to 1370.

At 1370, the fulfillment solution is designed based on the fulfillmentsolution blueprint. The flow then proceeds to 1380.

At 1380, the fulfillment solution is generated based on the fulfillmentsolution blueprint. The flow then ends.

Thus, in one embodiment, a service design and order fulfillment systemcan provide an organizational schema that can be used to design andgenerate a fulfillment solution, where the organization schema caninclude a configuration of order layers, provider functions, andinterfaces. Such a configuration can support business agility byenabling: (a) end-to-end fulfillment of orders for a wide variety ofproducts and services; (b) comprehensive order lifecycle management,including revision cancellations and fallout management, as well astransparent order and status visibility; and (c) decoupling of variouslayers of a service design and order fulfillment system, which canlocalize an impact of business changes and can reduce a scope of bothreconfiguration and testing following a change, and which has a positiveside effect of reducing an incidence of change-induced order fallout.

According to another embodiment, a service design and order fulfillmentsystem can provide commercial decoupling, where one or more productofferings are separated from fulfillment processes and associated onlyindirectly with a set of building blocks, such as productspecifications. Associating fulfillment logic with productspecifications can allow a desirable proliferation of commercialofferings while minimizing changes to a fulfillment process. One of theprimary mechanisms of the decoupling is a use of an intermediary serviceorder. Further, a fulfillment solution blueprint can be designed in partto enable commercial decoupling, as well as other types of decoupling.

FIG. 14 illustrates a block diagram of an entity hierarchy 1400,according to an embodiment of the invention. Entity hierarchy 1400 canbe utilized to effectuate a commercial decoupling, as entity hierarchy1400 creates separate layers of data, where the data that relates tocommercial offerings is decoupled from data that relates to a service orproduct that is provisioned to a customer. According to an embodiment, aplurality of entities can be defined within entity hierarchy 1400, whereeach entity includes a distinct subset of data, and where one entity canbe mapped to another entity. In certain embodiments, entity hierarchycan be part of a technical catalog.

In the illustrated embodiment of FIG. 14, entity hierarchy 1400 includesa product specification (i.e., product) 1410. As previously described, aproduct specification is an entity that represents a type of productoffering, and can be used to facilitate reuse of attributes and logicassociated with one or more product offerings. More specifically, aproduct specification represents all or a subset of the capabilities ofa customer-facing service specification.

Entity hierarchy 1400 also includes a simple offering 1420. Aspreviously described, a simple offering is a commercially viable andcommercially indivisible sales catalog item. A simple offering canestablish a promise to a customer and can represent a variety ofcommercial items, such as physical goods, services, service features,discounts, or pricing items. Simple offerings can be made available tosell solo, within a bundled or promotional offering, or both. Accordingto an embodiment, one or more simple offerings can be created based on aproduct specification.

Entity hierarchy 1400 also includes a bundled offering 1430. Aspreviously described, a bundled offering is an aggregation of one ormore simple offerings, other bundled offerings, and or commercializationlogic to facilitate selling and contracts. According to an embodiment,one or more bundled offerings can be created based on a simple offering.In certain embodiments, a bundled offering can include other bundledofferings in addition to, or instead of, simple offerings.

Entity hierarchy 1400 also includes a promotional offering 1440. Aspreviously described, a promotional offering is a special type ofbundled offering that offers reuse under different commercial andcontractual terms. Examples of commercial and contractual terms caninclude customer segments, time periods, and penalties associated withdiscontinuing the promotional offering. According to an embodiment, apromotional offering can be created based on one or more simpleofferings, one or more bundled offerings, or a combination therein.

Entity hierarchy 1400 also includes customer-facing servicespecification (i.e., customer-facing service) 1450. As previouslydescribed, a “customer-facing service” is a technology-agnosticabstraction of a holistic capability from a perspective of a serviceprovider (as opposed to a perspective of an end user) that facilitatesservice commercialization, fulfillment and management. A customer-facingservice can be realized through one or more technical solutions, where atechnical solution is comprised of one or more resources and/orresource-facing services. Thus, a customer-facing service defines theservice related features of commercial value that can be made availableto a market through one or more product offerings. Thus, a singlecustomer-facing service can be utilized regardless of a number ofproduct offerings (either simple, bundled, or promotional) that thecustomer-facing service is offered through. As also previouslydescribed, a customer-facing service specification is an entity thatrepresents a type of customer-facing service, and can be used tofacilitate reuse of attributes and logic associated with one or morecustomer-facing services.

A customer-facing service specification does not include data thatdescribes a product offering utilized to offer the customer-facingservice. Instead, a customer-facing service specification can be mappedto one or more product specifications, where a product offering (eithersimple, bundled, or commercial) can include the one or more productspecifications. In one embodiment, the mapped one or more productofferings, can be defined as a “commercial offering.” In one embodiment,a customer-facing service specification can be mapped to one or morecommercial offerings, and a commercial offering can be selected torepresent the customer-facing service specification at design-time.Thus, a customer-facing service described within a customer-facingservice specification can be completely decoupled from the commercialofferings of the customer-facing service described within one or moresimple offerings, bundled offerings, or promotional offerings. Further,a customer-facing service specification can also be mapped to one ormore resource-facing service specifications, one or more resourcespecifications, or a combination therein.

Entity hierarchy 1400 also includes resource-facing servicespecification (i.e., resource-facing service) 1460. As previouslydescribed, a resource-facing service is a technology-specific,vendor-agnostic abstraction of a capability from a perspective of aservice provider (as opposed to a perspective of an end user). Thus, aresource-facing service represents a meaningful capability associatedwith one or more resources. A resource-facing service may also combinecapabilities from other finer-grained resource-facing services. As alsopreviously described, a resource-facing service specification is anentity that represents a type of resource-facing service, and can beused to facilitate reuse of attributes and logic associated with one ormore resource-facing services.

Entity hierarchy 1400 also includes resource specification (i.e.,resource) 1470. As previously described, a resource is a part of aprovider's infrastructure, CPE utilized directly or indirectly by aservice, or a good that may be procured by the market in the form of aproduct. A resource can be physical and it can be realized through theprovider's infrastructure or as a CPE. Alternatively, a resource can belogical and it can be realized directly as a configuration (viasoftware) of physical resources, or it may be used to facilitate theconfiguration of the network or the interactions with a third-partysupplier or partner. As also previously described, a resourcespecification is an entity that represents a type of resource, and canbe used to facilitate reuse of attributes and logic associated with oneor more resources. In one embodiment, a resource-facing servicespecification can be mapped to one or more resource specifications. Inan alternate embodiment, a resource-facing service specification can bemapped to other resource-facing service specifications in addition to,or instead of, resource specifications.

FIG. 15 illustrates an example product offering 1500 and an exampleproduct specification to customer-facing service specification mapping,according to an embodiment of the invention. According to theembodiment, product offering 1500 is a bundled offering that includesthree simple offerings (i.e., simple offerings 1501, 1502, and 1503),and four product specifications (i.e., product specifications 1510,1511, 1512, and 1513). Further, product specifications 1510 and 1511 aremapped to customer-facing service specification 1520, and productspecification 1512 is mapped to customer-facing service specification1521. In the illustrated embodiment, product specification 1513 is notmapped to a customer-facing service specification. According to anembodiment, a customer order can be generated, where a first customerorder line of the customer order includes a product offering based onproduct specification 1510, a second customer order line of the customerorder includes a product offering based on product specification 1511, athird customer order line of the customer order includes a productoffering based on product specification 1512, and a fourth customerorder line of the customer order includes a product offering based onproduct specification 1513. Further, according to the embodiment, aspart of the fulfillment of the customer order, a customer order can betransformed into a service order, where a first service order line ofthe service order includes a customer-facing service based oncustomer-facing service specification 1520, and a second service orderline of the service order includes a customer-facing service based oncustomer-facing service specification 1521.

FIG. 16 illustrates an example product specification to fulfillmentpattern mapping for product offering 1500, according to an embodiment ofthe invention. As previously described, a fulfillment pattern includesmetadata that defines a set of one or more fulfillment functions and oneor more dependencies. According to the embodiment, productspecifications 1510 and 1511 are mapped to fulfillment pattern 1610.Product specification 1512 is further mapped to fulfillment pattern1620, and product specification 1513 is further mapped to fulfillmentpattern 1630. Thus, according to the embodiment, product offering 1500is decoupled from fulfillment patterns 1610, 1620, and 1630. This meansthat product offering 1500 can be modified without requiringmodifications to fulfillment patterns 1610, 1620, or 1630. For example,one or more commercial attributes (such as price) can be modified forproduct offering 1500 without requiring modifications to fulfillmentpatterns 1610, 1620, or 1630. Further, one or more new product offerings(either simple, bundled, or promotional) can be created based on one ormore of product specifications 1510, 1511, 1512, or 1513 withoutrequiring modifications to fulfillment patterns 1610, 1620, or 1630.

FIG. 17 illustrates an example product specification to fulfillment flowmapping for an example customer order 1710, according to an embodimentof the invention. According to the embodiment, customer order 1710includes customer order line 1711 which includes a product offeringbased on product specification 1510 of FIG. 15 (“Broadband PS”).Customer order 1710 further includes customer order line 1712 whichincludes a product offering based on product specification 1511 of FIG.15 (“Bandwidth PS”). Customer order 1710 further includes customer orderline 1713 which includes a product offering based on productspecification 1512 of FIG. 15 (“Email Service PS”). Customer order 1710further includes customer order line 1714 which includes a productoffering based on product specification 1513 of FIG. 15 (“Offer ChangePS”). Further, customer order lines 1711, 1712, 1713, and 1714 each mapto fulfillment flow 1720, where fulfillment flow 1720 is based onfulfillment patterns 1610, 1620, or 1630. According to an embodiment, anorchestration plan can be generated based on fulfillment flow 1720,where the orchestration plan can fulfill customer order 1710. Thus,according to the embodiment, product offering 1500 of FIG. 15 isdecoupled from fulfillment flow 1720. This means that product offering1500 of FIG. 15 can be modified without requiring modifications tofulfillment flow 1720. For example, one or more commercial attributes(such as price) can be modified for product offering 1500 withoutrequiring modifications to fulfillment flow 1720. Further, one or morenew product offerings (either simple, bundled, or promotional) can becreated based on one or more of product specifications 1510, 1511, 1512,or 1513 of FIG. 15 without requiring modifications to fulfillment flow1720. According to the embodiment, customer order 1710 can be furtherorchestrated, fulfilled, transformed, or otherwise processed.

FIG. 18 illustrates an example customer-facing service specification tofulfillment pattern mapping, according to an embodiment of theinvention. According to the embodiment, customer-facing servicespecifications 1520 and 1521 are mapped to fulfillment pattern 1810.Thus, according to the embodiment, product offering 1500 of FIG. 5 isdecoupled from fulfillment pattern 1810. This means that productoffering 1500 of FIG. 15 can be modified without requiring modificationsto fulfillment pattern 1810. For example, one or more commercialattributes (such as price) can be modified for product offering 1500without requiring modifications to fulfillment pattern 1810. Further,one or more new product offerings (either simple, bundled, orpromotional) can be created based on one or more of customer-facingservice specifications 1520 and 1521 without requiring modifications tofulfillment pattern 1810.

FIG. 19 illustrates an example customer-facing service specification tofulfillment flow mapping for an example service order 1910, according toan embodiment of the invention. According to the embodiment, serviceorder 1910 includes service order line 1911 which includes acustomer-facing service based on customer-facing service specification1520 of FIG. 15 (“Broadband Internet Access CFSS”). Service order 1910further includes service order line 1912 which includes acustomer-facing service based on customer-facing service specification1521 of FIG. 15 (“Email Service CFSS”). Further, service order lines1911 and 1912 each map to fulfillment flow 1920, where fulfillment flow1920 is based on fulfillment pattern 1810 of FIG. 18. According to anembodiment, an orchestration plan can be generated based on fulfillmentflow 1920, where the orchestration plan can fulfill service order 1910.Thus, according to the embodiment, product offering 1500 of FIG. 15 isdecoupled from fulfillment flow 1920. This means that product offering1500 of FIG. 15 can be modified without requiring modifications tofulfillment flow 1920. For example, one or more commercial attributes(such as price) can be modified for product offering 1500 withoutrequiring modifications to fulfillment flow 1920. Further, one or morenew product offerings (either simple, bundled, or promotional) can becreated based on one or more of customer-facing service specifications1520 and 1521 of FIG. 15 without requiring modifications to fulfillmentflow 1920. According to the embodiment, service order 1910 can befurther orchestrated, fulfilled, transformed, or otherwise processed.

FIG. 20 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention. The flow begins, and proceeds to 2010. At2010, a product offering is defined that includes one or more productspecifications. Each product specification includes metadata thatdefines a product that is provided. The product offering furtherincludes metadata that defines one or more commercial attributes. Incertain embodiments, the product offering is one of: a simple offering,a bundled offering, or a promotional offering. The flow then proceeds to2020.

At 2020, the one or more product specifications are mapped to one ormore fulfillment patterns. Each fulfillment pattern includes metadatathat defines a set of one or more fulfillment functions and one or moredependencies. The flow then proceeds to 2030.

At 2030, a customer order is generated that includes one or morecustomer order lines. Each customer order line includes a product actionand a product offering that is based on a product specification. Incertain embodiments, the customer order is an order for communicationservices. The flow then proceeds to 2040.

At 2040, the customer order is fulfilled using a fulfillment flow basedon the one or more fulfillment patterns mapped to the one or moreproduct specifications. In certain embodiments, the fulfillment of thecustomer order can include generating an orchestration plan based on thefulfillment flow, and executing the orchestration plan. The flow thenproceeds to 2050.

At 2050, the product offering is modified, where the modification to theproduct offering does not require a modification to the fulfillment flowused to fulfill the customer order. In certain embodiments, the productoffering is modified by modifying the one or more commercial attributesof the product offering. In other embodiments, the product offering ismodified by creating a new product offering based on at least one of theone or more product specifications. In other embodiments, the productoffering is modified by creating a new product offering based on one ormore existing product offerings. The flow then proceeds to 2060.

At 2060, the one or more product specifications are mapped to one ormore customer-facing service specifications. Each customer-facingservice specification includes metadata that defines a customer-facingservice that is provided. In certain embodiments, the product offering,the one or more product specifications, and the one or morecustomer-facing service specifications are each part of an entityhierarchy stored within an enterprise catalog, where the productoffering is stored in a commercial catalog, and the one or more productspecifications, as well as the one or more customer-facing servicespecifications, are stored within a technical catalog. The flow thenproceeds to 2070.

At 2070, the one or more customer-facing service specifications aremapped to one or more fulfillment patterns. The flow then proceeds to2080.

At 2080, the customer order is transformed into a service orderincluding one or more service order lines. Each service order lineincludes a service action and a customer-facing service based on acustomer-facing service specification. The flow then proceeds to 2090.

At 2090, the service order is fulfilled using a fulfillment flow basedon the one or more fulfillment patterns mapped to the one or morecustomer-facing service specifications. In certain embodiments, thefulfillment of the customer order can include generating anorchestration plan based on the fulfillment flow, and executing theorchestration plan. The flow then proceeds to 2095.

At 2095, the product offering is modified, where the modification to theproduct offering does not require a modification to the fulfillment flowused to fulfill the service order. In certain embodiments, the productoffering is modified by modifying the one or more commercial attributesof the product offering. In other embodiments, the product offering ismodified by creating a new product offering based on at least one of theone or more product specifications. In other embodiments, the productoffering is modified by creating a new product offering based on theproduct offering. The flow then ends.

Thus, in one embodiment, a service design and order fulfillment systemcan effectively decouple a product offering metadata entity from afulfillment flow used to fulfill both a customer order and a serviceorder. An introduction of product offerings within a sales catalog couldbe done without needing to make any changes in order management orwithin an OSS component. This could allow service providers the agilityto respond to market conditions in a single day as opposed to lengthycycles that extend to weeks and months otherwise.

According to another embodiment, a service design and order fulfillmentsystem can provide a format and semantic definition of a service order,where the service order is a primary request interface into afulfillment solution for a wide variety of communications/informationservices. The interface is defined around a customer-facing service,which can provide decoupling between commercial offers and theunderpinning technology implementations. A service order can be definedin terms of a specific kind of action. Further, a service ordercalculation provider function can generate this type of order.

As previously described, order fulfillment can utilize multiple ordersubject transformations via a set of one or more order layers. A firstorder layer can be a customer order layer (i.e., customer layer). Asecond order layer can be a service order layer (i.e., a service layer).A third order layer can be a technical order layer (also identified as atechnical layer). Each order layer can define a layer of an overallfulfillment solution, and each order layer can be configured toorchestrate a type of order among multiple provider functions,fulfillment system types, and fulfillment providers.

More specifically, a customer layer can be configured to orchestrate acustomer order, and to transform a customer order into a service order.A customer order can include one or more customer order lines. Eachcustomer order line can include a product action on a product offeringbased on a product specification, where the product offering is arepresentation of a sales catalog item along with one or more commercialattributes. Further, a service order can include one or more serviceorder lines. Each service order line can include a service action on acustomer-facing service based on a product specification, where thecustomer-facing service is a technology-agnostic abstraction of aholistic capability from a perspective of a service provider thatfacilitates service commercialization, fulfillment and management.

Thus, a service order can be considered a technology-agnosticrepresentation of a customer order. More specifically, a service orderis a way to represent a customer order in a technology-agnostic mannerthat is eventually represented as a technical order for fulfillment.This is because the service order is not required to include anytechnical attributes. Instead, the technical attributes can be includedwithin a technical order, and a technical order can be generated that isbased on the service order. Thus, the service order can be used toshield the customer layer from any technical changes. In other words, anoutput of the customer layer (i.e., a service order) does not need to bemodified in light of any technical changes within a technical layer.Similarly, the service order can also be used to shield the technicallayer from any commercial changes. In other words, an input of thetechnical layer (i.e., a service order) does not need to be modified inlight of any commercial changes within a customer layer. Thus, a serviceorder can be defined as a canonical representation of an action takenupon a customer-facing service, independent of commercial variations andindependent of technical variations. This allows a service layer toabstract a customer layer from a technical layer. A service order isfurther described in greater detail below.

Further, a service layer can be configured to orchestrate a serviceorder, and to generate a technical order. A technical order can includeone or more technical order lines. Each technical order line can includea technical action on a resource-facing service based on aresource-facing service specification, or a technical action on aresource based on a resource specification. A resource-facing service isa technology-specific, vendor-agnostic abstraction of a capability froma perspective of a service provider, and a resource is a part of aprovider's infrastructure, a CPE that is utilized directly or indirectlyby a service, or a good that may be procured by the market in the formof a product. Furthermore, a technical layer can be configured toorchestrate a technical order.

FIG. 21 illustrates an example service order 2110, an example customerorder 2120, and an example technical order 2130, according to anembodiment of the invention. According to the illustrated embodiment, anentity model 2100 includes a broadband service product offering 2101,where broadband service product offering is mapped to two productspecifications: a broadband product specification 2102 and a broadbandbandwidth product specification 2103. Further, broadband productspecification 2102 and broadband bandwidth product specification 2103are both mapped to a broadband internet access customer-facing servicespecification 2104. Even further, broadband internet accesscustomer-facing service specification 2104 is mapped to a number ofresources and resource-facing service specifications, which includes DSLresource-facing service specification 2105.

According to the embodiment, service order 2110 is a canonicalrepresentation of a service action taken on a customer-facing servicesubject. In the illustrated embodiment, service order 2110 includes an“UPDATE” service action on broadband internet access customer-facingservice specification 2104. The UPDATE service action modifies abandwidth value of broadband internet access customer-facing servicespecification 2104. In the illustrated embodiment, the UPDATE serviceaction modifies a bandwidth value of broadband internet accesscustomer-facing service specification 2104 from a prior value of “1Mbps” to a new value of “5 Mbps.”

In one embodiment, service order 2110 is a result of a transformation ofcustomer order 2120. Customer order 2120 is a canonical representationof product action on a product subject. In the illustrated embodiment,customer order 2120 includes a “DELETE” product action on broadbandservice product offering 2101 (i.e., delete “Basic Internet Access” fromthe broadband service product), and also includes an “ADD” productaction on broadband service product offering 2101 (i.e., add “PremiumInternet access” to the broadband service product). Thus, the UPDATEservice action on broadband internet access customer-facing servicespecification 2104 is a technology-agnostic representation of both theDELETE product action and the ADD product action on broadband serviceproduct offering 2101. In other words, in order to delete “BasicInternet Access” from the broadband service product and add “PremiumInternet Access” to the broadband service product, a service design andorder fulfillment system updates a broadband internet accesscustomer-facing service by modifying a bandwidth value of the broadbandinternet access customer-facing service from a prior value of “1 Mbps”to a new value of “5 Mbps.” Further, even if the change of bandwidth isrepresented differently on customer order 2120, such as a change to anattribute, service order 2110 would still include the UPDATE serviceaction on broadband internet access customer-facing servicespecification 2104. Thus, service order 2110 is a technology-agnosticrepresentation of customer order 2120.

Further, in one embodiment, technical order 2130 can be generated basedon service order 2110. Technical order 2130 is a canonicalrepresentation of a technical action taken on a technical subject (i.e.,a resource-facing service subject or a resource subject). In theillustrated embodiment, technical order 2130 includes a “MODIFY DSLBANDWIDTH” technical action on DSL resource-facing service specification2105. Thus, the MODIFY DSL BANDWIDTH technical action on DSLresource-facing service specification 2105 is a technology-specificrepresentation of the UPDATE service action on broadband internet accesscustomer-facing service specification 2104. In other words, in order toupdates a broadband internet access customer-facing service, a servicedesign and order fulfillment system modifies a bandwidth value of theDSL resource-facing service. Technical order 2130 is one of manypossible technical orders that vary by technology (e.g., DSL, DOCSIS,fiber, LTE), and by context (such as whether a customer is a residentialcustomer or a business customer). The logic used to create anappropriate technical order can dependent on a stable service orderinput and takes into consideration a state of inventory, infrastructure,and other context. This way, a single service order can result indifferent technical orders if executed for different contexts. Thus,technical order 2130 is a technology-specific representation of serviceorder 2110.

FIG. 22 illustrates an example of a plurality of service order lines ofservice order 2200, according to an embodiment of the invention. Serviceorder 2200 includes service order line 2210 and service order line 2220.Service order line 2210 includes a service action “ADD,” a subject name“Broadband Service”, a fulfillment item code that references a broadbandinternet access customer-facing service specification, a commercialinventory identity “AI-123456-1.1,” and a set of attributes (i.e.,Technology=Default; Download Speed=3096; Upload Speed=1024; QoS=Data).Thus, service order line 2210 performs an ADD service action on abroadband internet access customer-facing service that is based on abroadband internet access customer-facing service specification. Serviceorder line 2220 includes a service action “ADD,” a subject name “EmailService,” a fulfillment item code that references an email servicecustomer-facing service specification, a commercial inventory identity“AI-123456-3.1,” and a set of attributes (i.e., Admin Account=admin; MaxNumber of Accounts=5). Thus, service order line 2220 performs an ADDservice action on an email service customer-facing service that is basedon an email service customer-facing service specification.

FIG. 23 illustrates an example customer-facing service specification tofulfillment pattern mapping, where each customer-facing servicespecification is part of a service order line of a service order,according to an embodiment of the invention. According to theembodiment, customer-facing service specifications 2310 and 2311 aremapped to fulfillment pattern 2320. Thus, according to the embodiment,fulfillment pattern 2320 can be used to generate a fulfillment flow thatcan be used to fulfill a service order that includes customer-facingservice specification 2310, customer-facing service specification 2311,or a combination therein.

FIG. 24 illustrates an example service order 2410 mapped to an examplefulfillment flow 2420, according to an embodiment of the invention.According to the embodiment, service order 2410 includes service orderline 2411 which includes a customer-facing service based oncustomer-facing service specification 1520 of FIG. 15 (“BroadbandInternet Access CFSS”). Service order 2410 further includes serviceorder line 2412 which includes a customer-facing service based oncustomer-facing service specification 1521 of FIG. 15 (“Email ServiceCFSS”). Further, service order lines 2411 and 2412 each map tofulfillment flow 2420, where fulfillment flow 2420 is based onfulfillment pattern 2320 of FIG. 23. According to an embodiment, anorchestration plan can be generated based on fulfillment flow 2420,where the orchestration plan can fulfill service order 2410. Accordingto the embodiment, service order 2410 can be further orchestrated,fulfilled, transformed, or otherwise processed. Further, a design andassign provider function can receive service order 2410 and generate oneor more service instances based on service order 2410. This can be doneby determining a future infrastructure state that meets the constraintsof service order 2410, and then determining and executing anorchestration plan to realize the future state.

FIG. 25 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention. The flow begins and proceeds to 2510. At2510, a service action is defined that includes metadata that defines apattern of a structured request to perform work on a customer-facingservice that is based on a customer-facing service specification. Theflow then proceeds to 2520.

At 2520, a customer-facing service specification is defined thatincludes metadata that defines a customer-facing service that isprovided. According to the embodiment, a customer-facing serviceincludes a technology-agnostic abstraction of a holistic capability. Theflow then proceeds to 2530.

At 2530, a service order is defined, where the service order includesone or more service order lines, and where each service order lineincludes a service action and a customer-facing service based on acustomer-facing service specification. In certain embodiments, eachservice order line of the service order is also defined. Also, incertain embodiments, the service order is an order for communicationservices.

In some embodiments, the service order is transformed from a customerorder, where the customer order includes a product action and a productoffering, and where the product offering is the subject of the productaction. In some of these embodiments, the product offering can includeone or more product specifications. In some of these embodiments, theservice order is a technology-agnostic representation of the customerorder. Further, in some of these embodiments, the service action of theservice order is a technology-agnostic representation of one or morecustomer order lines of the customer order. The flow then proceeds to2540.

At 2540, an orchestration plan is generated that fulfills the serviceorder based on a fulfillment flow. In some of these embodiments, thefulfillment flow includes one or more fulfillment patterns that aremapped to the customer-facing service specification. The flow thenproceeds to 2550.

At 2550, a technical order is generated based on the service order,where the technical order includes a technical action and one of: aresource-facing service specification, or a resource specification. Theflow then proceeds to 2560.

At 2560, a service instance configuration is generated based on theservice order. The flow then ends.

Thus, in one embodiment, a service design and order fulfillment systemcan provide a service order, where a service order includes an actionthat is taken on a customer-facing service. Thus, an introduction of anewer technology to replace legacy technology (such as a 4G network toreplace a 3G network) requires only additional design and assignfunctionality to translate from an existing customer-facing service to atechnical service defined for the newer technology. This means that theintroduction of newer technology does not require any changes in amapping from a product specification to a customer-facing servicespecification. Because no changes to the customer-facing service arerequired, design and assign functionality can be based on a small set ofdurable service actions and customer-facing services. This can localizechanges to the fewest layers of a fulfillment solution, reduce a numberof mappings and a volume of logic, and keep mapping and logic simplerand hence more manageable. This can lead to a faster time to market.

According to another embodiment, a service design and order fulfillmentsystem can provide a fulfillment action (i.e., action), where an actionis defined as format and method for expressing requests betweencomponents of the service design and order fulfillment system, using astandardized pattern adaptable to various contexts within a fulfillmentsolution. One or more actions can be a basis of defining orders, such asa customer order, a service order, or a technical order.

FIG. 26 illustrates a general form of an action specification 2600 foran action, according to an embodiment of the invention. As describedbelow in greater detail, FIG. 27 illustrates an action specification2700 (i.e., service action 2700) as a more specific form of actionspecification 2600. Action specification 2600 is a general form of apattern or template. As described below in greater detail, a morespecifically defined action specification, such as action specification2720 (i.e., service action 2720) of FIG. 27, is a pattern or templatethat can be instantiated as a specific request. More specifically,action specification 2600 can serve as a general form of a pattern ortemplate that, where more specifically defined, can be transformed intoprocess logic when a more specifically defined action specification thatis based on action specification 2600 is instantiated. As is describedbelow in greater detail, action specification 2600 can be morespecifically defined by defining elements of action specification 2600,such as data 2610, subject 2620, or target 2630. Further, as previouslydescribed, an action is a structured request to perform work. Thus, anaction includes metadata that defines the pattern or template of thestructured request to perform work, where the format of the metadata isan action specification of a general form of action specification 2600.Further, action specification 2600 can serve as a pattern or templatefor more specifically-defined action specifications (such as actionspecification 2720 of FIG. 27).

Actions may be specified with varying degrees of specialization based onthe specificity of the action specification, providing flexibility indeclaring the semantics that are commonly understood by a requestor anda responder in a particular dialog. For example, if an actionspecification only includes generalized information, then the actionspecification (and the resulting action) can be considered generic,where the action can apply to a large set of subject types that varybroadly in nature. However, if the action specification includesspecific information, then the action specification (and the resultingaction) can be considered specific, where the action can only apply to asmall set of subject types (or a single subject type) whose naturevaries more narrowly. Thus, a level of specificity of an action is aspectrum varying from a generic pattern to a more specific pattern to aspecific subject type. In certain embodiments, a specific instance of anaction is an order line of an order.

According to the embodiment, action specification 2600 includes data2610 and subject 2620, and optionally includes target 2630. Data 2610 isdata that defines the request to perform work. By defining the requestto perform work, data 2610 can constrain the boundaries of actionspecification 2600. More specifically, data 2610 can include an actiontype, an action name, an action code, and a parameter list. An actiontype is a type identifier that identifies a type of the action. Theaction type can contextualize action specifications (such as actionspecification 2600) according to subject and can constrain valid actioncode verbs for an action specification. An action name is an actionidentifier that identifies the action. An action code is a predefinedcode, where the action code can take the format of a verb notation, andwhere the action code can be selected from a set of predefined verbs(such as, for example, ADD, MOVE, CHANGE, SUSPEND, RESUME, DISCONNECT).In an alternate embodiment, an action code can defined rather than beingselected from a set of predefined verbs. A set of predefined verbs canbe defined based on an action type. An action code can be an action codetemplate that refers to one or more action codes. A parameter list is alist of one or more parameters for carrying information as input to oroutput from the work to be performed by the request. The parameter listcan be a parameter template that refers to one or more parameters.Further, the one or more parameters can be inferred based on specificinformation defined for action specification 2600 (such as specificinformation defined for subject 2620) or can be explicitly defined.Thus, for example, different parameters lists for a specific action, andspecific subject, can be defined in a catalog. By selecting a specificaction and subject, a specific instantiation of one or more parameterscan inferred dynamically from a generic pattern. Alternatively, one ormore parameters can be specifically defined, and no inference isrequired.

Subject 2620 is an entity that is (or a set of entities that are) actedupon by the action. Subject 2620 can be defined generically to include asubject template that references a set of one or more entityspecifications, or subject 2620 can be defined to solely include aspecific entity specification. Examples of specific entityspecifications for subject 2620 can include a product specification, acustomer-facing service specification, a resource-facing servicespecification, or a resource specification.

Target 2630 is an entity, role, or individual (or a set of entities,roles, or individuals) to which a request to perform work is to berelayed. Thus, target 2630 can identify where the action is to takeplace. Target 2630 can be defined generically to include a targettemplate that references a set of one or more specifications, or target2630 can be defined to solely include a specific specification. Anexample of a specific specification for target 2630 can be a resourcespecification. As previously described, target 2630 is optional, and insome embodiments, action specification 2600 does not include target2630.

Thus, action specification 2600 allows an action to be expressed usingthe following format: “Apply Action-Code to Subject [at Target] usingParameterList.” This framework can provide semantic clarity for avariety of dialogs between a requestor and a responder. Using actionspecification 2600, the service design and order fulfillment system canexpress valid requests for a context, conversion of requests in onecontext to requests in another context, derivation of the requests thatcorrespond to state changes, and dependencies between requests that canbe considered when orchestrating the requests.

Further, in some embodiments, actions can be categorized by an orderlayer of a fulfillment solution blueprint. More specifically, actionscan be categorized into product actions (where an instance of a productaction can be included within a customer order line), service actions(where an instance of a service action can be included within a serviceorder line), and technical actions (where an instance of a technicalaction can be included within a technical order line). Product actions,service actions, and technical actions can each have a different set ofpotential action codes.

In certain embodiments, each action may also have some aspects of itsaction specification pre-defined, causing the action to be a specificaction. For example, an action can be specific to a specific subject oraction code. The more specific the definition of an action, the morelimited its use is to a narrow context, such as a specific function.Conversely, the action can be a completely generic pattern, requiringthat both a subject and an action code be provided when the action isinstantiated.

According to certain embodiments, different categories of actions can beutilized to define a fulfillment solution. Examples of these categoriesof actions are now described in greater detail. One example categoryincludes service layer generic actions that are applicable to anycustomer-facing service subject. Another example category includesservice layer actions that are specific to a particular customer-facingservice subject, but require an action code to be specified. Actionsfrom these two action categories can serve as a template for serviceorder lines of a service order. Another example category includesservice layer actions that are specific both to a subject and an actioncode. An example action of this action category is “Add_DSL” which candefine a parameter list specific to an “ADD” action code and specific toa DSL resource-facing specification subject. Actions from this actioncategory can be utilized in a design and assign provider function.Another example category includes technical layer generic actions thatare applicable to any resource-facing service subject or any resourcesubject. Actions from this action category can serve as a template fortechnical order lines of a technical order. Another example categoryincludes technical layer actions that are specific both to a subject andan action code. An example action of this action category is“AActivate_GSM_Subscriber” which can define a parameter list specific toa “CREATE” action code and specific to a GSM_Subscriptionresource-facing service specification subject. Actions from this actioncategory can be utilized in a technical order activation providerfunction. Actions from this action category can also serve as a templatefor technical order lines of a technical order.

FIG. 27 illustrates an example of a service action 2700, according to anembodiment of the invention. Service action 2700 is an example of ageneric action that has a generic pattern. More specifically, ratherthan including a specific action code, service action 2700 includes anaction code template, “ServiceAction-Code.” The action code templatereferences one or more service action codes defined within serviceaction codes 2740. Examples of service action codes in the illustratedembodiment include “ADD,” “CHANGE,” “MOVE,” “SUSPEND,” “RESUME,” and“DISCONNECT.” Thus, a service action code defined within service actioncodes 2740 can be derived from the action code template,“ServiceAction-Code.” In certain embodiments, the action code templatesreferences service action codes 2740 because an action type of action2700 is “ServiceAction.” Further, service action 2700 includes subject2710, where subject 2710 is a subject template (specifically, acustomer-facing service template). The customer-facing service templateof subject 2710 references a set of one or more customer-facing servicespecifications. Thus, any defined customer-facing service specificationcan be derived from the customer-facing service template of subject2710. Service action 2700 further includes a parameter list template,where the one or more parameters of the parameter list of service action2700 can be derived based on an instance of the customer-facing servicetemplate of subject 2710. Thus, service action 2700 can be expressedusing the following format: “Apply ServiceAction-Code to CFS usingParameterListDerivedFromSubject.”

FIG. 27 further illustrates service action 2720, where service action2720 is an example of a more specialized action that has a morespecialized pattern, and where service action 2720 can be derived fromservice action 2700. According to an embodiment, a specialized patterncan be derived from a generic pattern by performing at least one of: (1)replacing an action code template with a more specific action codetemplate that only references a subset of the one or more action codesthat are referenced by the generic action code template; (2) replacing aparameter list template with a more specific parameter list templatethat only references a subset of the one or more parameters referencedby the generic parameter list template; or (3) replacing a subjecttemplate with a more specific subject template that only references asubset of the one or more entity specifications referenced by thegeneric subject template.

More specifically, according to the illustrated embodiment, serviceaction 2720 includes an action name, “DDMobileSub.” Similar to serviceaction 2700, service action 2720 does not include a specific actioncode, but instead includes an action code template,“ServiceAction-Code.” The action code template references one or moreservice action codes defined within service action codes 2740. Further,service action 2720 includes subject 2730, where subject 2730 is amobile subscription template, and where a mobile subscription is acustomer-facing service. The mobile subscription template of subject2730 can reference a set of one or more mobile subscriptionspecifications. Thus, the mobile subscription template of subject 2730replaces the customer-facing service template of subject 2710. Serviceaction 2720 further includes a parameter list template that includes theparameters, “IMSI,” “TN,” “Roaming,” and “Voicemail,” where an instanceof service action 2720 can include values for the parameters. Theseparameters can be derived from the mobile subscription template ofsubject 2730. Thus, the parameter list template of service action 2720replaces the parameter list template of service action 2700. Serviceaction 2720 can further be expressed using the following format: “ApplyServiceAction-Code to Mobile Subscription using IMSI, TN, Roaming,Voicemail.”

According to the embodiment, service action 2720 can be instantiatedinto one or more service order lines, where a service order lineincludes a specific instance of a service action. By instantiatingservice action 2720 into a service order line, the following can beperformed: (1) using the action code template of service action 2720 toselect an action code; (2) using the parameter list template of serviceaction 2720 to populate one or more parameters with one or more values;and (3) using the subject template of service action 2720 to select aninstance of an entity specification. FIG. 27 illustrates two examples ofservice order lines that include instances of service action 2720:service order lines 2750 and 2760. Service order line 2750 includes: aservice action code, “ADD”; a subject, “Subscription-42”; and aparameter list, “20699542,” “+336555555,” “Y,” and “Y.” Service orderline 2760 includes: a service action code, “UPDATE”; a subject,“Subscription-79,” and a parameter list, “20699661,” “+33655550055,”“N,” and “Y.”

FIG. 28 illustrates two examples of service actions (i.e., serviceaction 2800 and service action 2830), according to an embodiment of theinvention. According to the illustrated embodiment, service action codesfrom FIG. 27 can be applied using an alternate pattern for a serviceaction. More specifically, service action 2800 is another example of amore specialized action that has a more specialized pattern, whereservice action 2800 can be derived from service action 2700 of FIG. 27.According to the illustrated embodiment, service action 2800 includes anaction name, “AddMobileSub.” Further, service action 2800 includes aspecific action code, “ADD.” Thus, the action code, “ADD,” replaces theaction code template of service action 2700. Service action 2800 alsoincludes subject 2810, where subject 2810 is a mobile subscriptiontemplate, and where a mobile subscription is a customer-facing service.The mobile subscription template of subject 2810 references a set of oneor more mobile subscription specifications. Thus, the mobilesubscription template of subject 2810 replaces the customer-facingservice template of subject 2710 of FIG. 27. Service action 2800 furtherincludes a parameter list template that includes the parameters, “IMSI,”“TN,” “Roaming,” and “Voicemail,” where an instance of service action2800 can include values for the parameters. These parameters can bederived from the mobile subscription template of subject 2810. Thus, theparameter list template of service action 2800 replaces the parameterlist template of service action 2700 of FIG. 27. Service action 2800 canfurther be expressed using the following format: “Apply ADD to MobileSubscription using IMSI, TN, Roaming, Voicemail.”

According to the embodiment, service action 2800 can be instantiatedinto one or more service order lines, where a service order lineincludes a specific instance of a service action. By instantiatingservice action 2800 into a service order line, a parameter list templatecan be replaced with one or more parameters, and a subject template canbe replaced with an entity specification. FIG. 28 illustrates an exampleof a service order line that includes an instance of service action2800: service order line 2820. Service order line 2820 includes: aservice action code, “ADD”; a subject, “Subscription-42”; and parametervalues, “20699542,” “+336555555,” “Y,” and “Y.”

Further, service action 2830 is another example of a more specializedaction that has a more specialized pattern, where service action 2830can be derived from service action 2700 of FIG. 27. According to theillustrated embodiment, service action 2800 includes an action name,“DDMobileSub.” Further, service action 2830 includes a specific actioncode, “UPDATE.” Thus, the action code, “UPDATE,” replaces the actioncode template of service action 2700 of FIG. 27. Service action 2830also includes subject 2840, where subject 2840 is a mobile subscriptiontemplate, and where a mobile subscription is a customer-facing service.The mobile subscription template of subject 2840 references a set of oneor more mobile subscription specifications. Thus, the mobilesubscription template of subject 2840 replaces the customer-facingservice template of subject 2710 of FIG. 27. Service action 2830 furtherincludes a parameter list template that includes the parameters,“Roaming” and “Voicemail,” where an instance of service action 2830 caninclude values for the parameters. These parameters can be derived fromthe mobile subscription template of subject 2840. Thus, the parameterlist template of service action 2800 replaces the parameter listtemplate of service action 2700 of FIG. 27. Service action 2830 canfurther be expressed using the following format: “Apply UPDATE to MobileSubscription using Roaming, Voicemail.”

According to the embodiment, service action 2830 can be instantiatedinto one or more service order lines, where a service order lineincludes a specific instance of a service action. By instantiatingservice action 2830 into a service order line, the parameter listtemplate can be used to populate one or more parameters with one or morevalues, and the subject template can be used to select an instance of anentity specification. FIG. 28 illustrates an example of a service orderline that includes an instance of service action 2830: service orderline 2850. Service order line 2850 includes: a service action code,“UPDATE”; a subject, “Subscription-79”; and a parameter list, “N” and“Y.”

FIG. 29 illustrates an example of two technical actions with differingdegrees of specialization (i.e., technical action 2900 and technicalaction 2930), according to an embodiment of the invention. Technicalaction 2900 is another example of a generic action that has a genericpattern. More specifically, rather than including a specific actioncode, technical action 2900 includes an action code template,“TechnicalAction-Code.” The action code template references one or moretechnical action codes defined within technical action codes 2960.Examples of technical action codes in the illustrated embodiment include“CREATE,” “MODIFY,” and “MOVE.” Thus, a technical action code definedwithin technical action codes 2960 can be derived from the action codetemplate, “TechnicalAction-Code.” In certain embodiments, the actioncode template references technical action codes 2960 because an actiontype of action 2900 is “TechnicalAction.” Further, technical action 2900includes subject 2910, where subject 2910 is a resource-facing serviceor resource template. The resource-facing service or resource templateof subject 2910 can reference a set of one or more resource-facingservice specifications or resource specifications. Thus, any definedresource-facing service specification or resource specification can bederived from the resource-facing service template of subject 2910.Technical action 2900 further includes a parameter list template thatcan reference a set of one or more parameters. Technical action 2900further includes target 2920, where target 2920 is a resource template.The resource template of target 2920 can reference a set of one or moreresource specifications. Thus, technical action 2900 can be expressedusing the following format: “Apply TechnicalAction-Code to RFSorResourceat Target using ParameterList.”

FIG. 29 further illustrates technical action 2930, where technicalaction 2930 is an example of a more specialized action that has a morespecialized pattern, and where technical action 2930 can be derived fromtechnical action 2900. As previously described, a specialized patterncan be derived from a generic pattern by performing at least one of: (1)replacing an action code template with a more specific action codetemplate that only references a subset of the one or more action codesthat are referenced by the generic action code template; (2) replacing aparameter list template with a more specific parameter list templatethat only references a subset of the one or more parameters referencedby the generic parameter list template; or (3) replacing a subjecttemplate with a more specific subject template that only references asubset of the one or more entity specifications referenced by thegeneric subject template. When an action specification includes atarget, a specialized pattern can also be derived from a generic patternby: (4) replacing a target template with a more specific target templatethat only references a subset of one or more specifications that arereferenced by the generic target template.

More specifically, technical action 2930 includes an action name,“CreateDSL.” Further, technical action 2930 includes a specific actioncode, “CREATE.” Thus, the action code, “CREATE,” replaces the actioncode template of technical action 2900. Technical action 2930 furtherincludes subject 2940, where subject 2940 is a DSL access template, andwhere a DSL access is a resource-facing service. The DSL access templateof subject 2940 references a set of one or more DSL accessspecifications. Thus, the DSL access template of subject 2940 replacesthe resource-facing service or resource template of subject 2910.Technical action 2930 further includes a parameter list template thatincludes the parameters, “PortID,” and “ServiceLocation,” where aninstance of technical action 2930 can include values for the parameters.Thus, the parameter list template of technical action 2930 replaces theparameter list template of technical action 2900. Technical action 2930further includes target 2950, where target 2950 is an access nodetemplate. The access node template of target 2950 can reference a set ofone or more access node specifications. Thus, the access node templateof target 2950 replaces the resource template of target 2920. Technicalaction 2930 can further be expressed using the following format: “ApplyCREATE to DSL Access at Access Node using PortID, ServiceLocation.”

According to the embodiment, technical action 2930 can be instantiatedinto one or more technical order lines, where a technical order lineincludes a specific instance of a technical action. By instantiatingtechnical action 2930 into a technical order line, the following can beperformed: (1) using the action code template of technical action 2930to select an action code; (2) using the parameter list template oftechnical action 2930 to populate one or more parameters with one ormore values; (3) using the subject template of technical action 2930 toselect an instance of an entity specification; and (4) using the targettemplate of technical action 2930 to select an instance of a resourcespecification. FIG. 29 illustrates two examples of technical order linesthat include instances of technical action 2930: technical order lines2970 and 2980. Technical order line 2970 includes: a technical actioncode, “CREATE”; a subject, “Access-543”; a parameter list, “983E4,”“Main St.”; and a target, “AN-94.” Technical order line 2980 includes: atechnical action code, “CREATE”; a subject, “Access-043”; a parameterlist, “3A327,” “Elm Street”; and a target, “AN-02.”

FIG. 29A illustrates an example of two activation actions (where anactivation action is a type of technical action) with differing degreesof specialization (i.e., activation action 2901 and activation action2931), according to another embodiment of the invention. Activationaction 2901 is another example of a generic action that has a genericpattern. More specifically, rather than including a specific actioncode, activation action 2901 includes an action code template,“ActivationAction-Code.” The action code template references one or moreactivation action codes defined within activation action codes 2961.Examples of technical action codes in the illustrated embodiment include“CREATE,” “MODIFY,” and “REMOVE.” Thus, an activation action codedefined within activation action codes 2961 can be derived from theaction code template, “ActivationAction-Code.” In certain embodiments,the action code template references activation action codes 2961 becausean action type of action 2901 is “ActivationAction.” Further, activationaction 2901 includes subject 2911, where subject 2911 is aresource-facing service or resource template. The resource-facingservice or resource template of subject 2911 can reference a set of oneor more resource-facing service specifications or resourcespecifications. Thus, any defined resource-facing service specificationor resource specification can be derived from the resource-facingservice template of subject 2911. Activation action 2901 furtherincludes a parameter list template that can reference a set of one ormore parameters. Activation action 2901 further includes target 2921,where target 2921 is a resource template. The resource template oftarget 2921 can reference a set of one or more resource specifications.Thus, activation action 2901 can be expressed using the followingformat: “Apply ActivationAction-Code to RFSorResource at Target usingParameterList.”

FIG. 29A further illustrates activation action 2931, where activationaction 2931 is an example of a more specialized action that has a morespecialized pattern, and where activation action 2931 can be derivedfrom activation action 2901. As previously described, a specializedpattern can be derived from a generic pattern by performing at least oneof: (1) replacing an action code template with a more specific actioncode template that only references a subset of the one or more actioncodes that are referenced by the generic action code template; (2)replacing a parameter list template with a more specific parameter listtemplate that only references a subset of the one or more parametersreferenced by the generic parameter list template; or (3) replacing asubject template with a more specific subject template that onlyreferences a subset of the one or more entity specifications referencedby the generic subject template. When an action specification includes atarget, a specialized pattern can also be derived from a generic patternby: (4) replacing a target template with a more specific target templatethat only references a subset of one or more specifications that arereferenced by the generic target template.

More specifically, activation action 2931 includes an action name,“AActivateDSL.” Further, activation action 2931 includes a specificaction code, “ActivateDSL.” Thus, the action code, “ActivateDSL,”replaces the action code template of activation action 2901. Activationaction 2931 further includes subject 2941, where subject 2941 is a DSLaccess template, and where a DSL access is a resource-facing service.The DSL access template of subject 2941 references a set of one or moreDSL access specifications. Thus, the DSL access template of subject 2941replaces the resource-facing service or resource template of subject2911. Activation action 2931 further includes a parameter list templatethat includes the parameters, “PortID,” “DownloadSpeed” and“UploadSpeed,” where an instance of activation action 2931 can includevalues for the parameters. Thus, the parameter list template ofactivation action 2931 replaces the parameter list template ofactivation action 2930. Activation action 2931 further includes target2951, where target 2951 is an access node template. The access nodetemplate of target 2951 can reference a set of one or more access nodespecifications. Thus, the access node template of target 2951 replacesthe resource template of target 2921. Activation action 2931 can furtherbe expressed using the following format: “Apply ActivateDSL to DSLAccess at Access Node using PortID, DownloadSpeed, UploadSpeed.”

According to the embodiment, activation action 2931 can be instantiatedinto one or more technical order lines, where a technical order lineincludes a specific instance of an activation action. By instantiatingactivation action 2931 into a technical order line, the following can beperformed: (1) using the action code template of activation action 2931to select an action code; (2) using the parameter list template ofactivation action 2931 to populate one or more parameters with one ormore values; (3) using the subject template of activation action 2931 toselect an instance of an entity specification; and (4) using the targettemplate of activation action 2931 to select an instance of a resourcespecification. FIG. 29A illustrates two examples of technical orderlines that include instances of activation action 2931: technical orderlines 2971 and 2981. Technical order line 2971 includes: an activationaction code, “ActivateDSL”; a subject, “Access-543”; a parameter list,“983E4,” “4096,” “1024”; and a target, “AN-94.” Technical order line2981 includes: a technical action code, “CREATE”; a subject,“Access-043”; a parameter list, “983E4,” “4096,” “1024”; and a target,“AN-02.”

FIG. 29B illustrates an example hierarchy of order lines (i.e., orderline hierarchy 2902), according to an embodiment of the invention. Orderline hierarchy 2902 includes technical order line 2912, where technicalorder line 2912 is a parent order line applicable to any deliverysystem. Order line hierarchy 2902 further includes technical order line2922, where technical order line 2922 is specific to an activationsystem. In alternate embodiments, order line hierarchy 2902 can includea plurality of technical order lines specific to an activation system.Order line hierarchy 2902 further includes technical order line 2932,where technical order line 2932 is specific to a WFM system. Inalternate embodiments, order line hierarchy 2902 can include a pluralityof technical order lines specific to a WFM system.

FIG. 30 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention. The flow begins, and proceeds to 3010. At3010, an action specification is defined that includes a pattern of astructured request to perform work on a subject. The flow then proceedsto 3020.

At 3020, data is defined for the action specification that includes anaction code template that references one or more action codes, and aparameter list template that references one or more parameters. The flowthen proceeds to 3030.

At 3030, the subject is defined for the action specification, where thesubject includes a subject template that references one or more entityspecifications. The flow then proceeds to 3040.

At 3040, a target is defined for the action specification, where thetarget includes a target template that references one or more resourcespecifications. In certain embodiments, 3040 can be omitted. The flowthen proceeds to 3050.

At 3050, an instance of an action is generated based on the actionspecification, where the pattern of the structured request to performwork is transformed into process logic configured to perform work on thesubject. In certain embodiments, the action is one of: a product action,a service action, or a technical action. In some of these embodiments,the instance of the action is included within one of: a customer orderline, a service order line, or a technical order line. In certainembodiments, the action is a component of a fulfillment solution, wherethe fulfillment solution includes a metadata-driven executable processthat fulfills an order. In some of these embodiments, the order is anorder for communication services.

Further, in certain embodiments, the generating the instance of theaction further includes: using the action code template to select anaction code, using the parameter list template to populate one or moreparameters with one or more values, and using the subject template toselect an instance of an entity specification. In some of theseembodiments, the one or more parameters can be inferred based on thesubject. In alternate embodiments, the generating the instance of theaction further includes: using a specific action code template thatreferences a subset of the one or more action codes to select an actioncode, using a specific parameter list template that references a subsetof the one or more parameters to populate one or more parameters withone or more values, and using a specific subject template thatreferences a subset of the one or more entity specifications to selectan instance of an entity specification. The flow then ends.

Thus, in one embodiment, a service design and order fulfillment systemcan provide an action, where an action is a pattern or template that canbe instantiated as a specific request, where an instance of an actioncan be included within an order line. Thus, an interface contract canutilize a set of actions to enable the functions/layers of anorchestration process to be decoupled, allowing requests to providevarying levels of latitude in framing their requests. This can allow fora standardized interface contract between systems and network elementsthat encapsulate how the interface contract is implemented so thatchanges to the implementation can be isolated and hidden. Further,actions can be defined declaratively, which can enable mapping of actionparameters to entity specifications and which can eliminate much of thecoding that is normally needed to perform this transformation. This canreduce overall solution complexity, and provide systems with neededagility to adapt to typical industry developments, such as deployment ofnew technologies, devices, network elements, partnerships, businessmodels, etc. This can further reduce cost and time needed to makenecessary changes. Additionally, the use of actions can improve clarityof requests through use of disciplined semantics, and can provide ahigher degree of dynamism through configuration of process logic usingtemplates.

According to another embodiment, a service design and order fulfillmentsystem can design a provider function such that a behavior of theprovider function is variable, driven by specifically structuredexternal metadata. Dynamic determination of a process flow can provideextreme versatility of the provider function while maintainingmanageability and reusability of the metadata. The dynamic,pattern-driven fulfillment approach can be utilized to design specificprovider functions, such as a customer order orchestration providerfunction, a service order orchestration provider function, a technicalorder orchestration provider function, a service order calculationprovider function, and a technical order calculation provider function.

FIG. 31 illustrates an example provider function 3100, according to anembodiment of the invention. A provider function (such as providerfunction 3100) is a logical component of a fulfillment solution thatoffers a generalized capability, where the provider function acts upon adefined input (such as input 3110) to generate a defined output (such asoutput 3120). In certain embodiments, input 3110 can be a customerorder, a service order, a technical order, one or more fulfillmentpatterns, or a combination therein. Further, in certain embodiments,output 3120 can be a service order, a technical order, or anorchestration plan.

According to the embodiment, provider function 3100 includes metadata3101 and a transformation sequence 3102. In an alternate embodiment,transformation sequence 3102 is omitted, and provider function 3100 onlyincludes metadata 3101. As is discussed below in greater detail,metadata 3101 includes a structured set of metadata, and transformationsequence 3102 includes a set of customizable process logic that isdesigned to be customized by metadata 3101, where the customizableprocess logic is structured within one or more stages. In certainembodiments, metadata 3101 includes a plurality of structured sets ofmetadata, where a set of metadata can be selected. Further, in certainembodiments, transformation sequence 3102 includes a plurality of setsof customizable process logic, where a set of customizable process logiccan be selected. Thus, the behavior of provider function 3100 in aparticular context can depend on metadata 3101 and transformationsequence 3102. This means that provider function 3100 can provide acapability that is customizable at runtime.

As is described below in greater detail, provider function 3100 can bedefined in a service-agnostic manner (i.e., provider function 3100 isnot coupled with a specific service or specific technology). Rather,provider function 3100 can utilize metadata (specifically, a fulfillmentpattern retrieved from a technical catalog, in certain embodiments) toprovide a generalized capability for a context of a specific stage of aprocess. Thus, the generalized capability provided by provider function3100 can be adaptable based on the fulfillment pattern. Further, thecapability provided by provider function 3100 can be dynamicallyproduced at runtime based on input (e.g., parameters and an informationstate of an order), based on metadata (e.g., fulfillment patternretrieved from technical catalog), and based on a subject (e.g., productspecification, customer-facing service specification, resource-facingservice specification, or resource specification). Thus, providerfunction 3100 can provide a separation of a fundamental fulfillmentpattern from metadata that causes the fulfillment pattern to perform aspecific function. Further, provider function 3100 can provide aseparation of metadata 3101 and transformation sequence 3102.

FIG. 32 illustrates another example provider function 3200, according toan embodiment of the invention. According to the embodiment, providerfunction 3200 includes metadata 3201, a transformation sequence 3202,and a base application 3203. Similar to the illustrated embodiment ofFIG. 31, metadata 3201 includes a structured set of metadata, andtransformation sequence 3202 includes a set of customizable processlogic. In certain embodiments, metadata 3101 includes a plurality ofstructured sets of metadata, where a set of metadata can be selected.Further, in certain embodiments, transformation sequence 3102 includes aplurality of sets of customizable process logic, where a set ofcustomizable process logic can be selected. Base application 3203includes base process logic that can be configured by metadata 3201 andtransformation sequence 3202.

According to the embodiment, provider function 3200 can be implementedin an environment of a specific software application by: (1) configuringbase application 3203 to select and utilize a set of customizableprocess logic from transformation sequence 3202; and (2) configuringbase application 3202 to select and utilized a set of metadata frommetadata 3201 based on a context of provider function 3200. Metadata3201 and transformation sequence 3202 are further described in greaterdetail in conjunction with FIGS. 33 and 34.

FIG. 33 illustrates metadata of an example provider function 3300,according to an embodiment of the invention. According to theembodiment, metadata of provider function 3300 can be in one of threecategories: entities 3301, discriminators 3302, and fulfillment patterns3303. Entities 3301 are entities that include metadata that defines acapability that is provided. In certain embodiments, entities 3301 caninclude at least one of: a product specification, a customer-facingservice specification, a resource-facing service specification, or aresource specification. According to the embodiment, a productspecification includes metadata that defines a product that is provided,a customer-facing service specification includes metadata that defines acustomer-facing service that is provided, a resource-facing servicespecification includes metadata that defines a resource-facing servicethat is provided, and a resource specification includes metadata thatdefines a resource that is provided. Further, entities 3301 canoptionally include one or more relationships or one or more mappings,where a relationship includes metadata that defines an associationbetween a first entity and a second entity, and a mapping includesmetadata that defines an association between a first entity, one or moreattributes of the first entity, or one or more attribute values of thefirst entity, and a second entity, one or more attributes of the secondentity, or one or more attribute values of the second entity.

Discriminators 3302 include metadata that define variants that can beused to select a fulfillment pattern from one or more fulfillmentpatterns. Discriminators 3302 can define request types or modes. Eachdiscriminator of discriminators 3302 can be associated with afulfillment pattern.

Fulfillment patterns 3303 include metadata that defines a set of one ormore fulfillment functions and one or more dependencies. Thus,fulfillment patterns are process flow declarations that can beconsidered abstractions of static process flows. This can provide for adeclaration of process flow that is more scalable. According to theembodiment provider function 3300 can dynamically generate a fulfillmentflow based on a selected fulfillment pattern. The dynamic generation ofa fulfillment flow from a selected fulfillment pattern is furtherdescribed in greater detail in conjunction with FIG. 35. Thus, acombination of one or more entity instances of entities 3301, along witha discriminator of discriminators 3302, results in a selection of afulfillment pattern of fulfillment patterns 3303. Further, the selectionof a fulfillment pattern of fulfillment patterns 3303 ultimatelydetermines a behavior of a transformation sequence of provider function3300. More specifically, the selected fulfillment pattern of fulfillmentpatterns 3303 is applied to a selected transformation sequence ofprovider function 3300 to dynamically generate a runtime process flow. Atransformation sequence is further described in greater detail inconjunction with FIG. 34.

FIG. 34 illustrates a transformation sequence of an example providerfunction 3400, according to an embodiment of the invention. According tothe illustrated embodiment, a transformation sequence of providerfunction 3400 is a multi-stage domain-agnostic algorithm, or processlogic, that can be designed to operate on any type of logical input,such as an order. Because the process logic is structured into one ormore stages, the process logic of each stage of the transformationsequence can operate on different sections of the information modelwithin each stage. Thus, a complex transformation can be broken downinto one or more simpler (and more stable) stages. This can makeprovider function 3400 relatively insensitive to a redefinition of adomain model, as provider function 3400 can be coded for stablepatterns, rather than the richness of a full complex sequence ofinstances. Further, by structuring a transformation sequence as discretestages, the discrete stages can be combined to support complextransformations.

FIG. 35 illustrates an example fulfillment flow 3510 for a providerfunction, where fulfillment flow 3510 is dynamically generated from afulfillment pattern 3500, according to an embodiment of the invention.Fulfillment pattern 3500 defines a set of one or more fulfillmentfunctions and one or more dependencies for a provider function.According to the embodiment, the provider function can evaluate thedependencies of fulfillment pattern 3500, and dynamically generatefulfillment flow 3510 based on fulfillment pattern 3500.

FIG. 36 illustrates a service design and order fulfillment system 3600that utilizes a plurality of provider functions, according to anembodiment of the invention. According to the embodiment, service designand order fulfillment system 3600 can provide order fulfillment througha complex fulfillment solution that can utilize multiple order subjecttransformations via a set of one or more order layers (i.e., customerlayer 3610, 3620, and 3630). Service design and order fulfillment system3600 can break down the complex functionality of the fulfillmentsolution through a plurality of provider functions. More specifically,service design and order fulfillment system 3600 can utilize a technicalcatalog 3640. Technical catalog 3640 includes an entity model 3650 thatincludes one or more entities (such as one or more productspecifications, one or more customer-facing service specifications, oneor more resource-facing service specifications, or one or more resourcespecifications). Technical catalog 3640 further includes a fulfillmentpattern set 3660 that includes one or more fulfillment patterns, wherethe one or more fulfillment patterns are mapped to the one or moreentities of entity model 3650. Service design and order fulfillmentsystem 3600 can further dynamically generate a provider function set3670, where each provider function of provider function set 3670 is acomponent of an overall fulfillment solution configured to fulfill anorder.

According to the embodiment, each provider function of provider functionset 3670 can be defined with an input and an output and can be definedto be service-agnostic. In some embodiments, each provider function ofprovider function set 3670 can also be action-agnostic. The one or moreprovider functions of provider function set 3670 can adapt to a contextthrough the use of one or more fulfillment patterns of fulfillmentpattern set 3660 defined within technical catalog 3640. Morespecifically, each provider function of provider function set 3670 canbe fitted with one or more fulfillment patterns of fulfillment patternset 3660. When an order is received, each provider function can read arequested action contained within the order, and determine whichfulfillment pattern(s) to apply based on the requested action plus otheroptional context. The actual fulfillment work can be composed andexecuted dynamically from the selected fulfillment pattern(s) throughgenerating a fulfillment flow based on the selected fulfillmentpattern(s).

FIG. 37 illustrates a provider function 3710 that utilizes one or moreitems of a technical catalog 3700, according to an embodiment of theinvention. According to the embodiment, provider function 3710 canselect one or more items from technical catalog to define the metadataof provider function 3710. Thus, by creating new items within technicalcatalog 3700, or by modifying or deleting existing items withintechnical catalog 3700, a provider function designer can modify thebehavior of provider function 3710.

FIG. 38 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention. The flow begins and proceeds to 3810. At3810, a structured set of metadata is defined for a provider function.In certain embodiments, the metadata includes one or more entitiesincluding metadata that defines a capability that is provided. In someof these embodiments, the metadata further includes one or morerelationships including metadata that defines an association between afirst entity and a second entity. In some of these embodiments, themetadata further includes one or more mappings including metadata thatdefines a first entity, one or more attributes of the first entity, orone or more attribute values of the first entity and a second entity,one or more attributes of the second entity, or one or more attributevalues of the second entity. In some of these embodiments, the metadatafurther includes one or more discriminators including metadata thatdefines one or more variants used to select a fulfillment pattern fromone or more fulfillment patterns. In some of these embodiments, themetadata further includes one or more fulfillment patterns includingmetadata that defines a set of one or more fulfillment functions and oneor more dependencies. Additionally, in certain embodiments, the definingthe structured set of metadata further includes defining a plurality ofstructured sets of metadata for the provider function, and selecting astructured set of metadata from the plurality of structured sets ofmetadata.

Further, in certain embodiments, the metadata is retrieved from atechnical catalog, such as a technical catalog 211 of FIG. 2. In some ofthese embodiments, the one or more entities of the metadata includes atleast one of: a product specification including metadata that defines aproduct that is provided; a customer-facing service specificationincluding metadata that defines a customer-facing service that isprovided; a resource-facing service specification including metadatathat defines a resource-facing service that is provided; or a resourcespecification including metadata that defines a resource that isprovided. The flow then proceeds to 3820.

At 3820, a transformation sequence including customizable process logicis defined for the provider function. The customizable process logic isstructured within one or more stages. In certain embodiments, thedefining the transformation sequence further includes defining aplurality of transformation sequences for the provider function, andselecting a transformation sequence from the plurality of transformationsequences. The flow then proceeds to 3830.

At 3830, base process logic is defined for the provider function. Theflow then proceeds to 3840.

At 3840, the base process logic is customized based on the metadata andthe transformation sequence. The flow then proceeds to 3850.

At 3850, a runtime process flow is dynamically generated for theprovider function based on the metadata and the transformation sequence.In certain embodiments, the dynamically generating the runtime processflow further includes selecting at least one fulfillment pattern fromthe one or more fulfillment patterns based on at least one entity fromthe one or more entities and at least one discriminator from the one ormore discriminators, and generating a fulfillment flow based on the atleast one selected fulfillment pattern.

Further, in certain embodiments, the provider function is a component ofa fulfillment solution including a metadata-driven executable processthat fulfills an order. In some of these embodiments, the order is anorder for communication services. The flow then ends.

Thus, in one embodiment, a service design and order fulfillment systemcan utilize one or more adaptable provider functions, where the one ormore provider functions can serve as components of an overallfulfillment solution. Thus, rather than continually refactoring code tosupport more product offerings, services, technologies, and devices,core functionality can be provided out-of-the-box and adapted to variantrequirements through a simple and reliable process of definingfulfillment patterns. Additional variants can be accommodated by reusingexisting patterns or by adding new patterns. This can eliminate servicedesign complexity, can eliminate a need to build different “stacks” fordifferent services/technologies, and can localize the impact of anychange to an implementation of one or more provider function fulfillmentpatterns.

According to another embodiment, a service design and order fulfillmentsystem can provide a service order calculation provider function thatderives orders for a wide range of communications/information servicesbased on orders for commercial offers. The service order calculationprovider function can be highly configurable using business-meaningfulmetadata, which can maximize business agility. The output of the serviceorder calculation provider function can have the form and semantics of aservice order, as previously described. The structure and behavior ofthe service order calculation provider function can be described interms of a pattern or template that can be transformed into processlogic, as previously described. Further, the components of drivingmetadata of the service order calculation provider function, as well asthe subject of the output of the service order calculation providerfunction, can be defined within a technical catalog, as previouslydescribed.

FIG. 39 illustrates an example service order calculation providerfunction 3900 that transforms a customer order 3910 into a service order3920, according to an embodiment of the invention. According to theembodiment, service order calculation provider function 3900 can includemetadata, where the metadata can be retrieved from technical catalog3901. The metadata can include one or more product specifications, oneor more customer-facing service specifications, one or morerelationships, and one or more mappings.

Further, according to the embodiment, service order calculation providerfunction 3900 can receive customer order 3910, where customer order 3910includes customer order lines 3911, 3912, and 3913. In the illustratedembodiments, customer order line 3911 includes a product action onproduct offering 1500 of FIG. 15 (“Broadband Service”), customer orderline 3912 includes a product action on simple offering 1501 of FIG. 15(“Basic Internet Access”), and customer order line 3913 includes aproduct action on simple offering 1502 of FIG. 15 (“EMailService”).Based on the metadata retrieved from technical catalog 3901, serviceorder calculation provider function 3900 can map product offering 1500of FIG. 15 to product specification 1510 of FIG. 15 (“Broadband”), canmap simple offering 1501 of FIG. 15 to product specification 1511 ofFIG. 15 (“Broadband Bandwidth”), and can map simple offering 1502 ofFIG. 15 to product specification 1512 of FIG. 15 (not illustrated inFIG. 39).

According to the embodiment, service order calculation provider function3900 can further generate service order 3920, transform customer orderlines 3911, 3912, and 3913 into service order lines 3921 and 3922, andpackage service order lines 3921 and 3922 within service order 3920. Aspart of the transformation, and based on the metadata retrieved fromtechnical catalog 3901, service order calculation provider function 3900can map product specifications 1510 and 1511 of FIG. 15 tocustomer-facing service specification 1520 of FIG. 15 (“BroadbandInternet Access”), and can map product specification 1512 of FIG. 15 tocustomer-facing service specification 1521 of FIG. 15 (“Email”). Also,as part of the transformation, service order calculation providerfunction 3900 can generate service order lines 3921 and 3922, whereservice order line 3921 includes a service action on a customer-facingservice that is based on customer-facing service specification 1520 ofFIG. 15 (“Broadband Internet Access”), and where service order line 3922includes a service action on a customer-facing service that is based oncustomer-facing service specification 1521 of FIG. 15 (“Email”).According to the embodiment, the product action of customer order line3911 and the product action of customer line 3912 can be transformedinto a service action of service order line 3921, and the product actionof customer order line 3913 can be transformed into a service action ofservice order line 3922.

FIG. 40 illustrates an example service order calculation providerfunction 4000, according to an embodiment of the invention. Serviceorder calculation provider function 4000 is a logical component of afulfillment solution that offers a capability of transforming a customerorder into a service order, where service order calculation providerfunction 4000 acts upon customer order 4010 to generate service order4020. In certain embodiments, service order calculation providerfunction 4000 follows a pattern-driven fulfillment model.

According to the embodiment, service order calculation provider function4000 includes metadata 4001 and a transformation sequence 4002. Metadata4001 includes a structured set of metadata, and transformation sequence4002 includes a set of customizable process logic that is designed to becustomized by metadata 4001, where the customizable process logic isstructured within one or more stages. In certain embodiments, metadata4001 includes a plurality of structured sets of metadata, where a set ofmetadata can be selected. Further, in certain embodiments,transformation sequence 4002 includes a plurality of sets ofcustomizable process logic, where a set of customizable process logiccan be selected. Additionally, in certain embodiments, service ordercalculation provider function 4000 includes a base application (notillustrated in FIG. 40), where the base application includes baseprocess logic that can be configured by metadata 4001, and that canselect transformation sequence 4002 to transform a customer order into aservice order.

In certain embodiments, metadata 4001 can be defined to include aspecifically structured set of specific metadata that is configured fortransforming a customer order into a service order. Such metadata caninclude one or more product specifications, one or more customer-facingservice specifications, one or more relationships between a productspecification and a customer-facing service specification, or one ormore mappings between one or more attributes of a product specificationand one or more attributes of a customer-facing service specification. Arelationship between a product specification and a customer-facingservice specification can be used to map the product specification tothe customer-facing service specification. More specifically, arelationship can be used to map one or more attributes of the productspecification to one or more attributes of the customer-facing servicespecification via one or more mappings. A relationship between a productspecification and a customer-facing service specification can be aprimary relationship or it can be an auxiliary relationship. A primaryrelationship is a relationship that can be used to create a new serviceorder line with a new customer-facing service specification based on anexisting customer order line with an existing product specification. Anauxiliary relationship is a relationship that can be used to modify anexisting service order line with an existing customer-facing servicespecification based on an existing customer order line with an existingproduct specification.

In some of these embodiments, the metadata of metadata 4001 can furtherinclude a single discriminator, and may not include any fulfillmentpatterns. Further, in embodiments where service order calculationprovider function 4000 includes a base application, the base applicationcan configure its base process logic based on the aforementionedmetadata. The aforementioned metadata is further described below ingreater detail in conjunction with FIG. 41.

Further, in certain embodiments, transformation sequence 4002 caninclude a single four-stage transformation sequence configured totransform one or more customer order lines of a customer order to one ormore service order lines of a service order. In embodiments whereservice order calculation provider function 4000 includes a baseapplication, the base application can configure its base process logicto select the aforementioned transformation sequence. The aforementionedtransformation sequence is further described below in greater detail inconjunction with FIG. 41.

FIG. 41 illustrates an example transformation sequence 4110 thattransforms a customer order into a service order, according to anembodiment of the invention. As previously described, a transformationsequence (such as transformation sequence 4110) can break down a complextransformation (such as transforming a customer order into a serviceorder) into a sequence of one or more stages. Each stage can receive aninput, can process the input, and can generate an output. Further, theprocessing the input can include at least a portion of thetransformation, and a final stage can generate the final output (such asa service order). Even further, each stage can be identified as atransformation stage.

In the illustrated embodiment, transformation sequence 4110 is a singlefour-stage transformation sequence configured to transform one or morecustomer order lines of a customer order to one or more service orderlines of a service order. However, this is an example embodiment, and inalternate embodiments, a transformation sequence that can be used totransform a customer order into a service order can have any number ofstages.

According to the illustrated embodiment, transformation sequence 4110can utilize metadata that includes one or more product specifications(identified in FIG. 41 as product specification 4120), one or morecustomer-facing service specifications (identified in FIG. 41 ascustomer-facing service specification 4130), one or more primaryrelationships and mappings between product specification 4120 andcustomer-facing service specification 4130 (identified in FIG. 41 asprimary mapping rules 4140), and one or more auxiliary relationships andmappings between product specification 4120 and customer-facing servicespecification 4130 (identified in FIG. 41 as auxiliary mapping rules4150).

According to the illustrated embodiment, in a first stage oftransformation sequence 4110 (illustrated in FIG. 41 as “Stage-1”), oneor more customer order lines can be transformed to one or more serviceorder lines using one or more primary service transformation rules. Theone or more primary service transformation rules can be based on primarymapping rules 4140, and can transform a product specification on acustomer order line to a customer-facing service specification on aservice order line.

In a second stage of transformation sequence 4110 (illustrated in FIG.41 as “Stage-2”), one or more children customer order line auxiliaryservice transformation rules can be applied to modify one or moreservice order lines. The one or more children customer order lineauxiliary service transformation rules can be based on auxiliary mappingrules 4150, and can modify one or more attributes of a customer-facingservice specification on a service order line based on one or moreattributes of a product specification on a corresponding customer orderline. In certain embodiments, the one or more children customer orderline auxiliary service transformation rules can be used to modify one ormore attributes of a customer-facing service specification on a serviceorder line based on one or more attributes of a product specification ona customer order line that is a child of a corresponding customer orderline.

In a third stage of transformation sequence 4110 (illustrated in FIG. 41as “Stage-3”), one or more sibling customer order line auxiliary servicetransformation rules can be applied to modify one or more service orderlines. The one or more sibling customer order line auxiliary servicetransformation rules can be based on auxiliary mapping rules 4150, andcan modify one or more attributes of a customer-facing servicespecification on a service order line based on one or more attributes ofa product specification on a corresponding customer order line. Incertain embodiments, the one or more children customer order lineauxiliary service transformation rules can be used to modify one or moreattributes of a customer-facing service specification on a service orderline based on one or more attributes of a product specification on acustomer order line that is a sibling of a corresponding customer orderline.

In a fourth stage of transformation sequence 4110 (illustrated in FIG.41 as “Stage-4”), one or more parent customer order line auxiliaryservice transformation rules can be applied to modify one or moreservice order lines. The one or more parent customer order lineauxiliary service transformation rules can be based on auxiliary mappingrules 4150, and can modify one or more attributes of a customer-facingservice specification on a service order line based on one or moreattributes of a product specification on a corresponding customer orderline. In certain embodiments, the one or more children customer orderline auxiliary service transformation rules can be used to modify one ormore attributes of a customer-facing service specification on a serviceorder line based on one or more attributes of a product specification ona customer order line that is a parent of a corresponding customer orderline.

FIG. 42 illustrates an example transformation rule set 4200, accordingto an embodiment of the invention. According to the embodiment,transformation rule set 4200 includes transformation rule subsets 4210,4220, and 4230. Transformation rule subset 4210 includes theattribute-value transformation rule, “CFS.AAA Account=PS.AAA Account.”This attribute-value transformation rule maps an “AAA Account” attributeof a customer-facing service specification to an “AAA Account” attributeof a corresponding product specification. The attribute-valuetransformation rule is a primary transformation rule. Further, theattribute-value transformation rule applies to product specification1510 of FIG. 15 (“Broadband PS”) and customer-facing servicespecification 1520 of FIG. 15 (“Broadband Internet Access CFSS”).

Transformation rule subset 4220 includes the following attribute-valuetransformation rules: “CFS.Download Speed.3072=PS.Download Speed.3Mbps;” “CFS.Download Speed.5120=PS.Download Speed.5 Mbps;” “CFS.DownloadSpeed.15360=PS.Download Speed.15 Mbps;” and “CFS.UploadSpeed.1024=PS.Upload Speed.1 Mbps.” The attribute-value transformationrule, “CFS.Download Speed.3072=PS.Download Speed.3 Mbps,” modifies a“Download Speed” attribute of a customer-facing service specification toa value of “3072,” when a “Download Speed” attribute of a correspondingproduct specification has a value of “3 Mbps.” The attribute-valuetransformation rule, “CFS.Download Speed.5120=PS.Download Speed.5 Mbps,”modifies a “Download Speed” attribute of a customer-facing servicespecification to a value of “5120,” when a “Download Speed” attribute ofa corresponding product specification has a value of “5 Mbps.” Theattribute-value transformation rule, “CFS.DownloadSpeed.15360=PS.Download Speed.15 Mbps,” modifies a “Download Speed”attribute of a customer-facing service specification to a value of“15360,” when a “Download Speed” attribute of a corresponding productspecification has a value of “15 Mbps.” The attribute-valuetransformation rule, “CFS.Upload Speed.1024=PS.Upload Speed.1 Mbps,”modifies an “Upload Speed” attribute of a customer-facing servicespecification to a value of “1024,” when an “Upload Speed” attribute ofa corresponding product specification has a value of “1 Mbps.” Thesefour attribute-value transformation rules are auxiliary transformationrules. Further, the four attribute-value transformation rules apply toproduct specification 1511 of FIG. 15 (“Bandwidth PS”), andcustomer-facing service specification 1520 of FIG. 15 (“BroadbandInternet Access CFSS”).

Transformation rule subset 4230 includes the attribute-valuetransformation rule, “CFS.Maximum Number of Accounts=PS.Maximum Numberof Accounts.” This attribute-value transformation rule maps a “MaximumNumber of Accounts” attribute of a customer-facing service specificationto a “Maximum Number of Accounts” attribute of a corresponding productspecification. The attribute-value transformation rule is a primarytransformation rule. Further, the attribute-value transformation ruleapplies to product specification 1512 of FIG. 15 (“Email Service PS”)and customer-facing service specification 1521 of FIG. 15 (“EmailCFSS”).

Thus, according to the embodiment, a modification to a product offering(such as a new bundled offering) does not require modifications to theprocess logic of a transformation sequence of a service ordercalculation provider function, as the process logic of thetransformation sequence is configured by the metadata of the serviceorder calculation provider function (which can be expressed in one ormore transformation rules). Thus, a transformation sequence can bedecoupled from one or more commercial offerings.

FIG. 43 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention. The flow begins and proceeds to 4310. At4310, a customer order is received, where the customer order includesone or more customer order lines. Each customer order line can include aproduct action and a product offering based on a product specification,where, in certain embodiments, a product specification can includemetadata that defines a product that is provided. The flow then proceedsto 4320.

At 4320, a structured set of metadata is defined. The structured set ofmetadata includes one or more product specifications, one or morecustomer-facing service specifications, one or more relationships, andone or more mappings. In certain embodiments, each product specificationcan include metadata that defines a product that is provided, eachcustomer-facing service specification can include metadata that definesa customer-facing service that is provided b, each relationship caninclude metadata that defines an association between a productspecification and a customer-facing service specification, and eachmapping can include metadata that defines an association between aproduct specification, one or more attributes of the productspecification, or one or more attribute values of the productspecification, and a customer-facing service specification, one or moreattributes of the customer-facing service specification, or one or moreattribute values of the customer-facing service specification.

Further, in certain embodiments, the one or more relationships caninclude at least one of: a primary relationship used to create a newservice order line including a new customer-facing service specificationbased on an existing customer order line including an existing productspecification; or an auxiliary relationship used to modify an existingservice order line including an existing customer-facing servicespecification based on an existing customer order line including anexisting product specification. The flow then proceeds to 4330.

At 4330, a transformation sequence including customizable process logicis defined. The customizable process logic is structured within one ormore stages. The flow then proceeds to 4340.

At 4340, base process logic is defined. The flow then proceeds to 4350.

At 4350, the base process logic is customized based on the metadata. Theflow then proceeds to 4360.

At 4360, the transformation sequence is selected using the customizedbase process logic. The flow then proceeds to 4370.

At 4370, the one or more customer order lines are transformed into oneor more service order lines based on the metadata and the transformationsequence. Each service order line can include a service action and acustomer-facing service based on a customer-facing servicespecification, where, in certain embodiments, the customer-facingservice specification can include metadata that defines acustomer-facing service that is provided. In certain embodiments, eachproduct action of a customer order line is transformed into a serviceaction of a service order line.

In certain embodiments, the transformation sequence includes fourstages, and the transforming the one or more customer order lines intothe one or more service order lines involves the following. In a firststage of the transformation sequence, the one or more customer orderlines can be transformed into one or more service order lines using oneor more primary service transformation rules. In certain embodiments,the one or more primary service transformation rules can transform aproduct specification on a customer order line to a customer-facingservice specification on a service order line.

In a second stage of the transformation sequence, the one or moreservice order lines can be modified using one or more children customerorder line auxiliary service transformation rules. In certainembodiments, the one or more children customer order line auxiliaryservice transformation rules modify one or more attributes of acustomer-facing service specification on a service order line based onone or more attributes of a product specification on a customer orderline that is a child of a corresponding customer order line.

In a third stage of the transformation sequence, the one or more serviceorder lines can be modified using one or more sibling customer orderline auxiliary service transformation rules. In certain embodiments, theone or more sibling customer order line auxiliary service transformationrules can modify one or more attributes of a customer-facing servicespecification on a service order line based on one or more attributes ofa product specification on a customer order line that is a sibling of acorresponding customer order line.

In a fourth stage of the transformation sequence, the one or moreservice order lines can be modified using one or more parent customerorder line auxiliary service transformation rules. In certainembodiments, the one or more parent customer order line auxiliaryservice transformation rules can modify one or more attributes of acustomer-facing service specification on a service order line based onone or more attributes of a product specification on a customer orderline that is a parent of a corresponding customer order line. The flowthen proceeds to 4380.

At 4380, a service order is generated, where the service order includesthe one or more service order lines. In certain embodiments, the serviceorder is an order for communication services. The flow then ends.

Thus, in one embodiment, a service design and order fulfillment systemcan provide a service order calculation provider function, that cantransform a customer order into a service order. The service design andorder fulfillment system can reduce a sensitivity of the service ordercalculation provider function to commercial and technical changes tolimited scenarios where a new type of service is introduced. This canafford service providers a high degree of agility at a very low cost.More specifically, the creation of new bundled offering generally doesnot require any changes to process logic, and an introduction of a newservice can be handled by simply introducing new mapping rules, asopposed to adding new process logic.

According to another embodiment, a service design and order fulfillmentsystem can provide a technical order calculation provider function thatgenerates a type of order (i.e., a technical order) that representsactivities required to realize a design of a communications/informationservice. The technical order calculation provider function can decouplework to be done in a network from a service order that triggered thework. A technical order that is generated by the technical ordercalculation provider function can be defined in terms of one or morefulfillment actions (i.e., actions), as previously described. Further,the technical order calculation provider function can be described interms of a pattern or template that can be transformed into processlogic, as previously described. Further, the components of drivingmetadata of the technical order calculation provider function, as wellas the subject of the output of the technical order calculation providerfunction, can be defined within a technical catalog, as previouslydescribed.

FIG. 44 illustrates an example technical order calculation providerfunction 4400 that generates a technical order 4420, according to anembodiment of the invention. According to the embodiment, technicalorder calculation provider function 4400 can use metadata, where themetadata can be retrieved from technical catalog 4401. The metadata caninclude one or more customer-facing service specifications, one or moreresource-facing service specifications, one or more resources, one ormore relationships, one or more mappings, and one or more actions.

Further, according to the embodiment, technical order calculationprovider function 4400 can receive service configuration 4410, whereservice configuration 4410 can include a configuration of one or moreresource-facing services and/or one or more resources. In certainembodiments, the configuration of one or more resource-facing servicesand/or one or more resources can be based on an upstream service order.More specifically, a design and assign provider function can receive aservice order and generate a service instance, where the serviceinstance can include a configuration of one or more resource-facingservices and/or one or more resources. In certain embodiments, theconfiguration of one or more resource-facing services and/or one or moreresources can represent a future state of a service according to theservice order. In these embodiments, technical order calculationprovider function 4400 can compare the configuration of one or moreresource-facing services and/or one or more resources that represents afuture state of a service with a configuration of one or moreresource-facing services and/or one or more resources that represents apresent state of the service. In certain embodiments, the service can bea customer-facing service.

Technical order calculation provider function 4400 can further generatea configuration delta that represents a change in the configuration ofone or more resource-facing services and/or one or more resources, wherethe change in the configuration realizes the configuration of one ormore resource-facing services and/or one or more resources thatrepresents the future state of the service. Technical order calculationprovider function 4400 can further generate one or more technicalactions that can effectuate the configuration delta (i.e., change theconfiguration of one or more resource-facing services and/or one or moreresources that represents a present state of the service into theconfiguration of one or more resource-facing services and/or one or moreresources that represents a future state of the service). In certainembodiments, at least a portion of the configuration delta can berepresented using one or more parameters of a technical action. In otherwords, in certain embodiments, at least a portion of the change in theconfiguration of one or more resource-facing services and/or one or moreresources is represented by a change in one or more parameter values ofone or more technical actions.

According to the embodiment, technical order calculation providerfunction 4400 can further generate technical order 4420, generatetechnical order lines 4421 and 4422 based on the one or more technicalactions, and package technical order lines 4421 and 4422 withintechnical order 4420. While two technical order lines are generated inthe illustrated embodiment, in other alternate embodiments, any numberof technical order lines can be generated. According to the illustratedembodiment, technical order line 4421 includes a plurality of actions ona resource-facing service that is based on resource-facing servicespecification 530 of FIG. 5 (“DSL”), and technical order line 4422includes a plurality of actions on a resource that is based on resourcespecification 532 of FIG. 5 (“DSL CPE”).

FIG. 45 illustrates an example technical order calculation providerfunction 4500, according to an embodiment of the invention. Technicalorder calculation provider function 4500 is a logical component of afulfillment solution that offers a capability of generating a technicalorder, where technical order calculation provider function 4000 actsupon a service configuration 4510 to generate technical order 4520. Incertain embodiments, technical order calculation provider function 4500follows a pattern-driven fulfillment model.

According to the embodiment, technical order calculation providerfunction 4500 uses metadata 4501 and a transformation sequence 4502.Metadata 4501 includes a structured set of metadata, and transformationsequence 4502 includes a set of customizable process logic that isdesigned to be customized by metadata 4501, where the customizableprocess logic is structured within one or more stages. In certainembodiments, metadata 4501 includes a plurality of structured sets ofmetadata, where a set of metadata can be selected. Further, in certainembodiments, transformation sequence 4502 includes a plurality of setsof customizable process logic, where a set of customizable process logiccan be selected. Additionally, in certain embodiments, technical ordercalculation provider function 4500 includes a base application (notillustrated in FIG. 45), where the base application includes baseprocess logic that can be configured by metadata 4501, and that canselect transformation sequence 4502 to generate a technical order.

In certain embodiments, metadata 4501 can be defined to include aspecifically structured set of specific metadata that is configured forgenerating a technical order. Such metadata can include one or moreresource-facing service specifications, one or more resourcespecifications, one or more relationships between a customer-facingservice specification and either a resource-facing service specificationor a resource, one or more relationships between a resource-facingservice specification and a resource specification, one or more mappingsbetween one or more attributes of a resource-facing servicespecification and one or more attributes of a customer-facing servicespecification, a resource-facing service specification or a resourcespecification, one or more mappings between one or more attributes of aresource specification, and one or more attributes of a customer-facingservice specification, a resource-facing service specification or aresource specification, one or more technical actions on aresource-facing service specification (which can include a parameter setassociated with each technical action), one or more technical actions ona resource specification (which can include a parameter set associatedwith each technical action), one or more parameter mappings (where aparameter mapping is a mapping from a configuration delta to a parameterof a parameter set associated with a technical action), one or moretechnical action recognition patterns (where a technical actionrecognition pattern is expressed in terms of changes to one or moreparameters of a technical action that are associated with aresource-facing service specification or a resource specificationthrough a technical action definition), one or more technical orderdefinitions, and one or more parameter set structures (where a parameterset structure is a structure within a technical order of a parameter setof a technical action). According to the embodiment, such metadata canbe used to interpret a configuration delta. Further, such metadata canbe used to determine how the configuration delta can be representedwithin one or more technical actions. Such metadata can also be used todetermine how the one or more technical actions can be formatted withinone or more technical order lines of a technical order (such astechnical order 4520). Further, such metadata can also be used todetermine to format the one or more technical order lines of a technicalorder (such as technical order 4520) can be used to determine an overallformat of a technical order (such as technical order 4520).

In some of these embodiments, the metadata of metadata 4501 can furtherinclude a single discriminator, and may not include any fulfillmentpatterns. Further, in embodiments where technical order calculationprovider function 4500 includes a base application, the base applicationcan configure its base process logic based on the aforementionedmetadata. The aforementioned metadata is further described below ingreater detail in conjunction with FIG. 46.

Further, in certain embodiments, transformation sequence 4502 caninclude a single five-stage transformation sequence configured togenerate a technical order. In embodiments where technical ordercalculation provider function 4500 includes a base application, the baseapplication can configure its base process logic to select theaforementioned transformation sequence. The aforementionedtransformation sequence is further described below in greater detail inconjunction with FIG. 46.

FIG. 46 illustrates an example transformation sequence that generates atechnical order, according to an embodiment of the invention. Aspreviously described, a transformation sequence (such as transformationsequence 4610) can break down a complex transformation (such asgenerating a technical order) into a sequence of one or more stages.Each stage can receive an input, can process the input, and can generatean output. Further, the processing the input can include at least aportion of the transformation, and a final stage can generate the finaloutput (such as a technical order). Even further, each stage can beidentified as a transformation stage.

In the illustrated embodiment, transformation sequence 4610 is a singlefive-stage transformation sequence configured to generate a technicalorder including one or more technical order lines. However, this is anexample embodiment, and in alternate embodiments, a transformationsequence that can be used to generate a technical order can have anynumber of stages.

According to the illustrated embodiment, transformation sequence 4610can utilize metadata that includes one or more resource-facing servicespecifications (identified in FIG. 46 as resource-facing servicespecifications 4620 and 4630), one or more resource specifications(identified in FIG. 46 as resource specifications 4640 and 4641), one ormore relationships and mappings between resource-facing servicespecification 4620 and resource-facing service specification 4630, oneor more relationships and mappings between resource-facing servicespecification 4620 and resource specification 4640, and one or morerelationships and mappings between resource-facing service specification4620 and resource specification 4641 (collectively identified in FIG. 46as compositional relationships 4650), one or more actions onresource-facing service specification 4620 (identified in FIG. 46 asactions 4660), one or more actions on resource-facing servicespecification 4630 (identified in FIG. 46 as actions 4670), and one ormore actions on resource specification 4640 (identified in FIG. 46 asactions 4680). In certain embodiments, transformation sequence 4610 canfurther utilize metadata that includes one or more parameter mappings,one or more technical action recognition patterns, one or more technicalorder definitions, and one or more parameter set structures (notillustrated in FIG. 46).

According to the illustrated embodiment, in a first stage oftransformation sequence 4610 (illustrated in FIG. 46 as “Stage-1”), aconfiguration delta can be calculated that represents a change in aconfiguration of one or more resource-facing services and/or one or moreresources. In certain embodiments, the configuration delta can becalculated by comparing a configuration of one or more resource-facingservices and/or one or more resources that represents a future state ofa service with a configuration of one or more resource-facing servicesand/or one or more resources that represents a present state of theservice. In certain embodiments, the service can be a customer-facingservice.

In some of these embodiments, the configuration of one or moreresource-facing services and/or one or more resources that represents afuture state of the customer-facing service is generated based on aservice order that includes one or more service order lines, where eachservice order line includes a service action and a customer-facingservice based on a customer-facing service specification. Morespecifically, one or more resource-facing services and/or one or moreresources that are within a scope of the customer facing service areidentified, and a configuration of the identified one or moreresource-facing services and/or one or more resources that represents afuture state of the customer-facing service (as described by thecorresponding service order line of the service order) is determined.The aforementioned configuration is compared to a configuration theidentified one or more resource-facing services and/or one or moreresources that represents a present state of the customer-facingservice, and a configuration delta is calculated, where theconfiguration delta represents a change in the configuration of theidentified one or more resource-facing services and/or one or moreresources.

In certain alternate embodiments, the configuration delta is simplyreceived from an external source, as opposed to being calculated. Inthese embodiments, the configuration delta can be based on a serviceorder that includes one or more service order lines, where each serviceorder line includes a service action and a customer-facing service basedon a customer-facing service specification.

In a second stage of transformation sequence 4610 (illustrated in FIG.46 as “Stage-2”), the configuration delta is analyzed, and a resourceparameters list delta is generated for each resource specification orresource-facing service specification for which one or more technicalactions are defined. The resource parameters list delta can include oneor more parameters of one or more technical actions that have changed.In certain embodiments, where the configuration delta does not includeany changes to any parameters of any technical actions, no resourceparameters list is generated.

In a third stage of transformation sequence 4610 (illustrated in FIG. 46as “Stage-3”), one or more technical actions are identified based on thechanges to the parameter set associated with the one or more resourcespecifications or one or more resource-facing services for which one ormore technical actions are defined, and the one or more technicalactions are generated, where each technical action is an action oneither a resource-facing service specification or a resource. Inembodiments where a resource parameters list delta has been generated,the parameter set for each technical action can be populated withappropriate parameters from the resource parameters list delta and theoverall configuration delta.

In a fourth stage of transformation sequence 4610 (illustrated in FIG.46 as “Stage-4”), one or more technical order lines are generated. Thegenerated technical actions are then packaged within the one or moretechnical order lines. In certain embodiments where the configurationdelta is based on a service order, the one or more technical order linescorrespond to the one or more service order lines of the service order.

In a fifth stage of transformation sequence 4610 (illustrated in FIG. 46as “Stage-5”), a technical order is generated, and the one or moregenerated technical order lines are packaged within the technical order.Further, in certain embodiments, supplementary information can beincluded within the one or more generated technical order lines of thetechnical order, such as identifiers used for correlation, dependencies,and targets. In addition, supplemental information may be retrieved fromthe service order and populated within the technical order.Subsequently, the generated technical order can be sent to a technicalorder activation provider function configured to receive the technicalorder and translate the technical order into one or more commandsequences delivered to one or more infrastructure elements.

In an example, a user of a communications service can call acommunications service provider and request to update bandwidth from 20MB/sec to 100 MB/sec. The user's request can be expressed in a customerorder as changing the user's service from “Gold service” to “Diamondservice.” The user's request can further be expressed in a service orderchanging a broadband service from a first speed to a second speed. Aservice order design and assign provider function can receive theservice order and determine that the user needs to be disconnected froma cable network and connected to a fiber network. A technical ordercalculation provider function can then determine all the technicalactions that are required to be done to achieve this future state of thenetwork. Such technical actions could include activation (activating auser account for the fiber network), work management (sending atechnician to the user's house to activate a device), etc.

Thus, according to certain embodiments, the technical order calculationprovider function can determine actual work that is to be performed on anetwork (or other infrastructure element). More specifically, thetechnical order calculation provider function can determine what isgoing to change on the infrastructure element, and can determine one ormore technical actions to effectuate the change. In these embodiments,the technical order calculation provider function can interpret theservice order (including the one or more service order lines, where eachservice order line includes a service action on a customer-facingservice based on customer-facing service specification) in order togenerate a configuration of one or more resource-facing services and/orone or more resources that represent a future state of theinfrastructure element. In other words, the technical order calculationprovider function can generate a configuration of one or moreresource-facing services and/or one or more resources that represent afuture state of the infrastructure element based on the service order.Subsequently, as previously described, the technical order calculationprovider function can compare a configuration of one or moreresource-facing services and/or one or more resources that represent afuture state of the infrastructure element with a configuration of oneor more resource-facing services and/or one or more resources thatrepresent a present state of the infrastructure element, and cangenerate a configuration delta based on the comparison. Thus, ratherthan generating the technical order based on the service order, thetechnical order calculation provider function can generate the technicalorder based on the configuration delta (i.e., the comparison of theconfiguration of one or more resource-facing services and/or one or moreresources that represent a future state of the infrastructure elementwith the configuration of one or more resource-facing services and/orone or more resources that represent a present state of theinfrastructure element.

FIG. 47 illustrates an example generation of a technical order based ona configuration delta, according to an embodiment of the invention. FIG.47 includes a configuration delta 4710, where configuration delta 4710can be associated with a service action that adds customer-facingservice specification 4711. According to the embodiment, configurationdelta 4710 represents a change between a future configuration of one ormore resource-facing services and/or one or more resources (identifiedas “Future Configuration 1” in FIG. 47) and a current configuration ofone or more resource-facing services and/or one or more resources(identified as “Current Configuration” in FIG. 47). Thus, because thecurrent configuration does not include any resource-facing services orresources, configuration delta 4710 includes resource-facing servicespecification 4712, and resource specifications 4713, 4714, 4715, 4716,and 4717, where configuration delta 4710 indicates that theaforementioned entities are to be added. According to the embodiment,while all entities of the future configuration that are to be added areincluded within configuration delta 4710, not all of the entities arethe subject of a technical action. Instead, some entities can bereferenced as enriching entities within a scope of an action centered onanother component.

FIG. 47 further includes technical action list 4720. Technical actionlist 4720 includes all possible technical actions against all relevantentities (i.e., resource-facing service specification 4712 and resourcespecification 4715). In the illustrated embodiment, technical actionlist 4720 includes technical actions 4721, 4722, and 4723.

FIG. 47 further includes calculate technical actions function 4730.Calculate technical actions function 4730 retrieves technical actions4721, 4722, and 4723 from technical action list 4720, and identifies themost appropriate technical action which will achieve the intended futureconfiguration of the resource specification or resource-facing servicespecification.

FIG. 47 further includes technical order line list 4740. Technical orderline list 4740 includes one or more technical order lines thatcorrespond to a set of technical actions identified to achieve anintended configuration change. In the illustrated embodiment, technicalorder line list 4740 includes technical order line 4741 (which isgenerated by identifying technical action 4721 as the appropriatetechnical action to achieve the intended configuration change,populating the relevant technical action parameters of technical action4721, and formatting technical action 4721 into technical order line4741), technical order line 4742 (which is generated by identifyingtechnical action 4722 as the appropriate technical action to achieve theintended configuration change, populating the relevant technical actionparameters of technical action 4722, and formatting technical action4722 into technical order line 4742), and technical order line 4743(which is generated by identifying technical action 4723 as theappropriate technical action to achieve the intended configurationchange, populating the relevant technical action parameters of technicalaction 4723, and formatting technical action 4723 into technical orderline 4743).

FIG. 48 illustrates another example generation of a technical orderbased on a configuration delta, according to an embodiment of theinvention. FIG. 48 includes a configuration delta 4810, whereconfiguration delta 4810 can be associated with a service action thatmoves customer-facing service specification 4711 to a new servicelocation. According to the embodiment, configuration delta 4810represents a change between a future configuration of one or moreresource-facing services and/or one or more resources (identified as“Future Configuration 2” in FIG. 48) and a current configuration of oneor more resource-facing services and/or one or more resources(identified as “Current Configuration” in FIG. 48). Thus, configurationdelta 4810 includes resource 4811 (where resource 4811 is being added),resource-facing service specification 4712 (where resource-facingservice specification 4712 is unchanged), resource 4714 (where resource4714 is being deleted), resource 4812 (where resource 4812 is beingadded), and resources 4715, 4716, and 4717 (where resources 4715, 4716,and 4717 are unchanged). Configuration delta 4810 further indicates thata relationship between customer-facing service specification 4711 andresource-facing service specification 4712 is being changed, and furtherindicates that a relationship between resource-facing servicespecification 4712 and resources 4714 and 4812 is also being changed.

FIG. 48 further includes technical action list 4820. Technical actionlist 4820 includes all possible technical actions against all relevantentities (i.e., resource-facing service specification 4712). In theillustrated embodiment, technical action list 4820 includes technicalaction 4821.

FIG. 48 further includes calculate technical actions function 4830.Calculate technical actions function 4830 identifies technical action4821 as being the most appropriate technical action to achieve anintended configuration change, and uses technical action 4821 to createa technical order line.

FIG. 48 further includes technical order line list 4840. Technical orderline list 4840 includes a technical order line that can be generated byidentifying a technical action as the appropriate technical action toachieve the intended configuration change, populating the relevanttechnical action parameters of the technical action, and formatting thetechnical action into the technical order line. In the illustratedembodiment, technical order line list 4840 includes technical order line4841, which is generated identifying technical action 4821 as theappropriate technical action to achieve the intended configurationchange, populating the relevant technical action parameters of technicalaction 4821, and formatting technical action 4821 into technical orderline 4841.

FIG. 49 illustrates another example generation of a technical orderbased on a configuration delta, according to an embodiment of theinvention. FIG. 49 includes a configuration delta 4910, whereconfiguration delta 4910 can be associated with a service action thatmoves customer-facing service specification 4711 to a new servicelocation. According to the embodiment, configuration delta 4910represents a change between a future configuration of one or moreresource-facing services and/or one or more resources (identified as“Future Configuration 3” in FIG. 49) and a current configuration of oneor more resource-facing services and/or one or more resources(identified as “Current Configuration” in FIG. 49). Thus, configurationdelta 4910 includes resource 4911 (where resource 4911 is being added),resource-facing service specification 4712 (where resource-facingservice specification 4712 is being deleted), resources 4714, 4715, and4716 (where resources 4714, 4715, and 4716 are being deleted), resources4912 and 4913 (where resources 4912 and 4913 are being added), andresource 4717 (where resource 4717 is unchanged). Configuration delta4810 further indicates that a relationship between customer-facingservice specification 4711 and resource-facing service specifications4712 and 4912 is being changed.

FIG. 49 further includes technical action list 4920. Technical actionlist 4920 includes all possible technical actions against all relevantentities (i.e., resource-facing service specification 4712, resource4715, and resource 4923). In the illustrated embodiment, technicalaction list 4920 includes technical actions 4921, 4922, 4923, 4924, and4925.

FIG. 49 further includes calculate technical actions function 4930.Calculate technical actions function 4930 identifies technical actions4921, 4922, 4923, 4924, and 4925 as being the most appropriate technicalactions to achieve an intended change and uses these technical actionsto create a technical order line.

FIG. 49 further includes technical order line list 4940. Technical orderline list 4940 includes one or more technical order lines that can begenerated by identifying a technical action as the appropriate technicalaction to achieve the intended configuration change, populating therelevant technical action parameters of the technical action, andformatting the technical action into a technical order line. In theillustrated embodiment, technical order line list 4940 includestechnical order line 4941 (which is generated by identifying technicalaction 4921 as the appropriate technical action to achieve the intendedconfiguration change, populating the relevant technical actionparameters of technical action 4921, and formatting technical action4921 into technical order line 4941), technical order line 4942 (whichis generated by identifying technical action 4922 as the appropriatetechnical action to achieve the intended configuration change,populating the relevant technical action parameters of technical action4922, and formatting technical action 4922 into technical order line4942), technical order line 4943 (which is generated by identifyingtechnical action 4923 as the appropriate technical action to achieve theintended configuration change, populating the relevant technical actionparameters of technical action 4923, and formatting technical action4923 into technical order line 4943), technical order line 4944 (whichis generated by identifying technical action 4924 as the appropriatetechnical action to achieve the intended configuration change,populating the relevant technical action parameters of technical action4924, and formatting technical action 4924 into technical order line4944), and technical order line 4945 (which is generated by identifyingtechnical action 4925 as the appropriate technical action to achieve theintended configuration change, populating the relevant technical actionparameters of technical action 4925, and formatting technical action4925 into technical order line 4945).

Thus, in the illustrated embodiment, moving the same customer-facingservice specification (i.e., customer-facing service specification 4711)to a different service location results in a different configurationdelta, and thus, results in very different technical order lines.

FIG. 50 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention. The flow begins, and proceeds to 5010. At5010, a structured set of metadata can be defined. The structured set ofmetadata includes one or more resource-facing service specifications,one or more resource specifications, one or more relationships, one ormore mappings, one or more technical actions, one or more parametersets; one or more parameter mappings, one or more technical actionrecognition patterns, one or more technical order definitions, and oneor more parameter set structures. In certain embodiments, eachresource-facing service specification can include metadata that definesa resource-facing service that is provided, and each resourcespecification can include metadata that defines a resource that isprovided.

Further, each relationship can include metadata that defines at leastone of: an association between a customer-facing service specificationand either a resource-facing service specification or a resourcespecification, or an association between a resource-facing servicespecification and a resource specification. Each mapping can includemetadata that defines at least one of: an association between acustomer-facing service specification, one or more attributes of thecustomer-facing service specification, or one or more attribute valuesof the customer-facing service specification, and resource-facingservice specification or resource specification, one or more attributesof the resource-facing service specification or resource specification,or one or more attribute values of the resource-facing servicespecification or resource specification, or an association between aresource-facing service specification, one or more attributes of theresource-facing service specification, or one or more attribute valuesof the resource-facing service specification, and a resourcespecification, one or more attributes of the resource specification, orone or more attribute values of the resource specification Eachtechnical action can include metadata that defines a pattern of astructured request to perform work on either a resource-facing servicebased on a resource-facing service specification or a resource based ona resource specification. The flow then proceeds to 5020.

At 5020, a transformation sequence including customizable process logicis defined. The customizable process logic is structured within one ormore stages. The flow then proceeds to 5030.

At 5030, base process logic is defined. The flow then proceeds to 5040.

At 5040, the base process logic is customized based on the metadata. Theflow then proceeds to 5050.

At 5050, the transformation sequence is selected using the customizedbased process logic. The flow then proceeds to 5060.

At 5060, a configuration delta is calculated, where a configurationdelta includes a change in a configuration of one or moreresource-facing services or one or more resources. In certainembodiments, the configuration delta is received. In other embodiments,rather than receiving the configuration delta, a configuration of one ormore resource-facing services or one or more resources that represents afuture state of a customer-facing service can be compared with aconfiguration of one or more resource-facing services or one or moreresources that represent a current state of the customer-facing service.The configuration delta can then be generated based on the comparison.Further, in certain embodiments, the configuration delta can be based ona service order that includes one or more service order lines, whereeach service order line includes a service action and a customer-facingservice based on a customer-facing service specification. The flow thenproceeds to 5070.

At 5070, one or more technical actions that effectuate the configurationdelta are generated. Each technical action includes metadata thatdefines a pattern of a structured request to perform work on aresource-facing service based on a resource-facing service specificationor a resource based on a resource specification. The pattern includes anaction identifier and a parameter set including one or more parametersfor the technical action. Each parameter includes one or more mappingsthat populates the parameter from the configuration delta. In certainembodiments, the generating the one or more technical actions can bebased on the metadata and the transformation sequence. The flow thenproceeds to 5080.

At 5080, one or more technical order lines are generated. Each technicalorder line includes a technical action and a resource-facing servicethat is based on a resource-facing service specification or a resourcethat is based on a resource specification. In certain embodiments, thegenerating the one or more technical order lines can be based on themetadata and the transformation sequence. The flow then proceeds to5090.

At 5090, a technical order is generated, where the technical orderincludes the one or more technical order lines. In certain embodiments,the technical order is an order for communication services.

In certain embodiments, the transformation sequence includes fivestages, and the generating the technical order involves the following.In a first stage of the transformation sequence, the configuration deltais received. In a second stage of the transformation sequence, aresource parameters list delta is generated, where the resourceparameters list delta includes one or more parameters of one or moretechnical actions that have changed. In a third stage of thetransformation sequence, the one or more technical actions aregenerated. In a fourth stage of the transformation sequence, the one ormore technical order lines are generated. In a fifth stage of thetransformation sequence, supplementary information is inserted withinthe one or more technical order lines, where the supplementaryinformation includes one or more identifiers, dependencies, targets, orparameters. The flow then ends.

Thus, in one embodiment, a service design and order fulfillment systemcan provide a technical order calculation provider function, that cangenerate a technical order based on a service order. This can allow theservice design and order fulfillment system to optimize work required todeliver an order. For example, the service design and order fulfillmentsystem can pinpoint the most optimal technical action to use to achievea certain change in a way that is agnostic to the service and productmodels. It is possible that a service action does not provide aconfiguration delta for one customer, a simple configuration delta foranother customer, and a complex configuration delta for yet anothercustomer. Further, the transformation sequence approach utilized by thetechnical order calculation provider function allows for a breakdown ofcomplex process logic into a series of steps that are not specific to aservice, technology, or action. Adding a new domain only requires addingnew definitions of catalog entities and technical actions, and does notrequire the addition of new process logic. This can provide businesseswith unprecedented agility to stay viable in changing markets.

According to another embodiment, a service design and order fulfillmentsystem can define process logic for a service order design and assignprovider function that designs communications/information services byselecting and assembling supporting components. The service order designand assign provider function can be encapsulated within a SRM system,and the service order design and assign provider function can bemodularized around a standardized set of entities. The service orderdesign and assign provider function can receive input in the form of aservice order, where a service order is previously described. Theservice order design and assign provider function can further includeone or more entities, actions, and/or relationships that are definedwithin a technical catalog, where a technical catalog is also previouslydescribed.

According to the embodiment, a service order design and assign providerfunction can create process logic, where the process logic can create aservice instance based on a service order. A service instance can becreated based on one or more components or building blocks, where eachcomponent can be associated with one or more modules, where each moduleincludes process logic for that component. Such components can one ormore entities, where the entities can be retrieved from a technicalcatalog. Further, such components can include one or morecustomer-facing service specifications, one or more resource-facingservice specifications, and/or one or more resource specifications.

FIG. 51 illustrates an order management workflow for a service designand order fulfillment system, according to an embodiment of theinvention. According to the illustrated embodiment, the service designand order fulfillment system includes an SOM component 5110, a SRMcomponent 5120, a TOM component 5130, an activation component 5140, andan ILEC/WFM component 5150.

SOM component 5110 can support service order decomposition,orchestration, and order lifecycle management. SOM component 5110 canfurther orchestrate fulfillment of a service order (such as serviceorder 5111) across SRM component 5120, TOM component 5130, activationcomponent 5140, and ILEC/WFM component 5150. More specifically, SOMcomponent 5110 can receive service order 5111 and generate a technicalorder based on service order 5111. SOM component 5110 can generate thetechnical order via design and assign function 5112 (“Design andAssign”), calculate technical actions function 5113 (“CalculateTechnical Actions), and technical order creation function 5114 (“CreateTechnical Order”). Design and assign function 5112 can invoke serviceorder design and assign provider function 5121 (“Design and AssignService Order”) of SRM component 5120. Further, calculate technicalactions function 5113 can invoke technical action calculation providerfunction 5122 (“Calculate Technical Action”) of SRM component 5120. Evenfurther, technical order creation function 5114 can invoke technicalorder fulfillment provider function 5131 (“Fulfill ProvisioningTechnical Order”) of TOM component 5130.

SRM component 5120 can perform a service order design and assignfunction via service order design and assign provider function 5121(“Design and Assign Service Order”). As is described below in greaterdetail, service order design and assign provider function 5121 candesign an instance of any service, such as a customer-facing service.SRM component 5120 can further perform a technical action calculationfunction via technical action calculation provider function 5122(“Calculate Technical Action”), as part of creating a technical order,where the technical order can be based on the service instance designedby service order design and assign provider function 5121.

TOM component 5130 can receive a technical order from SOM component 5130and can orchestrate the technical order among various service design andorder fulfillment system components, such as activation component 5140and ILEC/WFM component 5150, via technical order fulfillment providerfunction 5131 (“Fulfill Provisioning Technical Order”).

Activation component 5140 can receive a technical order line of atechnical order and perform a technical order activation fulfillmentfunction via technical order activation provider function 5141 (“FulfillActivation Technical Order”).

ILEC/WFM component 5150 is an example of a technical layer componentthat can perform one or more technical actions (such as an install localloop technical action) via technical action function 5151 (“InstallLocal Loop”).

According to the embodiment, SOM component 5110 can invoke multiple SRMcomponents via design and assign function 5112, where each SRM componentcan perform a complete design and assign activity for a portion of workto be performed. Thus, SOM component 5110 only requires knowledge ofwhich SRM component is responsible for which portion of work, and SOMcomponent 5110 is more independent of any particular domain. Thus,design and assign function 5112 can remain domain-agnostic.

FIG. 52 illustrates an example design of an entity, where instances ofthe entity are designed using the specification of the entity as apattern, according to an embodiment of the invention. According to theembodiment, a subject entity can be designed as a configuration thatincludes one or more entities, where two or more entities can have aparent-child relationship. According to the embodiment, an instance ofthe subject can be designed such that the subject's component instancesconform to the parent-child relationship between their specifications.In embodiments where a service is a customer-facing service, theentities can include at least one of: a customer-facing service(patterned by a customer-facing service specification), aresource-facing service (patterned by a resource-facing servicespecification), or a resource (patterned by a resource specification).In the illustrated embodiment, the arrangement of entities includesentities 5210, 5220, 5230, 5240, 5250, and 5260. Entity 5210 can be aparent of entity 5220, and thus, entity 5220 can be a child of entity5210. Entity 5220 can be a parent of entities 5230 and 5240, and thus,entities 5230 and 5240 can be children of entity 5220. Entity 5230 canbe a parent of entities 5250 and 5260, and thus, entities 5250 and 5260can be children of entity 5230. In certain embodiments, entity 5210 canbe a customer-facing service specification, entity 5220 can be aresource-facing service specification, and entities 5230, 5240, 5250,and 5260 can either be a resource-facing service specification or aresource specification.

According to the embodiment, each entity of entities 5210, 5220, 5230,5240, 5250, and 5260 can be treated as a subject of a design. Morespecifically, a design context can be established for each entity, andan instance of each entity can be designed within the design context.The designing of each entity can be performed modularly and/orrecursively. For example, an instance of entity 5210 can first bedesigned. An instance of entity 5220 as a component of entity 5210 cansubsequently be designed. An instance of entity 5230 as a component ofentity 5220 can subsequently be designed. An instance of entity 5240 asa component of entity 5220 can subsequently be designed.

For example, as illustrated in FIG. 52, a first design context can beestablished for entity 5220 within configuration environment 5270, whereentity 5220 is the subject of the first design context. An instance ofentity 5220 can be designed as a component of an instance of entity5210, where the instance of entity 5220 can be assembled from allrelevant sub-components (i.e., instances of entities 5230 and 5240). Aspart of designing the instance of entity 5220, a second design contextcan be established for entity 5230 within configuration environment5270, where entity 5230 is the subject of the second design context. Aninstance of entity 5230 can be designed as a component of entity 5220,where the instance of entity 5230 can be assembled from all relevantsub-components (i.e., instances of entities 5250 and 5260). This can berepeated for each of entities 5210, 5220, 5230, 5240, 5250, and 5260.All of the design contexts can be created within a single configurationenvironment (i.e., configuration environment 5270). Further, all of thedesign contexts can have access to a library of one or more durableversatile functions, supporting functionality that designs an instanceof an entity, such as lookup, association, instantiation, update ofobjects, etc. Further, each design context has access to the libraryindependent of their domain context. Further, each instance of eachentity of entities 5210, 5220, 5230, 5240, 5250, and 5260 can beexecuted within a single execution environment (i.e., executionenvironment 5280) using a versatile task/workflow engine.

FIG. 53 illustrates example process logic structured around an exampledomain entity model, according to an embodiment of the invention.According to the embodiment, designing an instance of an entity caninclude creating process logic for the entity that creates or updates aninstance of the entity, where the process logic can be encapsulatedwithin a module. The illustrated embodiment of FIG. 53 includes entities5310, 5320, 5330, and 5340. Entity 5310 is associated with process logicmodule family 5311, where process logic module family 5311 includes aset of one or more process logic modules, and where each process logicmodule of process logic module family 5311 includes process logic thatcreates or updates an instance of entity 5310. Entity 5320 is associatedwith process logic module family 5321, where process logic module family5321 includes a set of one or more process logic modules, and where eachprocess logic module of process logic module family 5321 includesprocess logic that creates or updates an instance of entity 5320. Entity5330 is associated with process logic module family 5331, where processlogic module family 5331 includes a set of one or more process logicmodules, and where each process logic module of process logic modulefamily 5331 includes process logic that creates an instance of entity5330. Entity 5340 is associated with process logic module family 5341,where process logic module family 5341 includes a set of one or moreprocess logic modules, and where each process logic module of processlogic module family 5341 includes process logic that creates or updatesan instance of entity 5340.

According to the embodiment, the process logic contained within eachmodule of process logic module family 5311 is specific to entity 5310.Similarly, the process logic contained within each module of processlogic module family 5321 is specific to entity 5320, the process logiccontained within each module of process logic module family 5331 isspecific to entity 5330, and the process logic contained within eachmodule of process logic module family 5341 is specific to entity 5340.Thus, an instance of a service can be designed by assembling entities5310, 5320, 5330, and 5340, and the instance of the service can beinstantiated by invoking the process logic contained within the one ormore modules of process logic module families 5311, 5321, 5331, and5341. Further, an instance of a service can be re-designed byrestructuring a configuration of entities 5310, 5320, 5330, and 5340,without requiring changes to the process logic contained within the oneor more modules of process logic module families 5311, 5321, 5331, and5341. Further, the process logic contained within the one or moremodules of module families 5311, 5321, 5331, and 5341 can be structuredusing a uniform format, regardless of where entities 5310, 5320, 5330,and 5340 appear in a domain model. Thus, a service can be modeled from aset of entities (such as entities 5310, 5320, 5330, and 5340), where theprocess logic for each entity can be expressed using the same uniformformat.

In the illustrated embodiment, entity 5310 is defined to have twocomponents (identified as “A.a” and “A.b”). Entity 5310 can be designedso that A.a references entity 5320, and A.b references either entity5330 or 5340. One of ordinary skill in the art would readily appreciatethat this is an example configuration of entities 5310, 5320, 5330, and5340, and that an instance of an entity can be designed according to anyconfiguration of one or more entities. Thus, a framework for modular andreusable process logic is provided to design an instance of a service,such as a customer-facing service, where an instance of a service caninclude a configuration of one or more entities, where the one or moreentities can include at least one of a customer-facing servicespecification, a resource-facing service specification, or a resource.

FIG. 54 illustrates an example creation of process logic for an instanceof a customer-facing service, according to an embodiment of theinvention. According to the embodiment, service order 5410 is received,where service order 5410 includes a service action to add acustomer-facing service entitled “Broadband Internet Access.” Accordingto the embodiment, a configuration for the customer-facing service isdefined within environment 5420, where the configuration includes aresource-facing service entitled “DSL,” a resource entitled “DSL_CPE” aresource entitled “DSL_Interface,” a resource entitled “ULL,” and aresource entitled “AAA.”

Furthermore, in accordance with the embodiment, module 5430 is created,where module 5430 includes process logic that creates an instance of thecustomer-facing service entitled “Broadband Internet Access” (i.e., acustomer-facing service specification). Module 5440 is furtherrecursively created within module 5430, where module 5440 includesprocess logic that creates an instance of the resource-facing serviceentitled “DSL” (i.e., a resource-facing service specification). Module5450 is further recursively created within module 5440, where module5450 includes process logic that creates an instance of the resourceentitled “DSL_CPE” (i.e., a resource specification). Module 5460 isfurther recursively created within module 5440, where module 5460includes process logic that creates an instance of the resource entitled“DSL_Interface” (i.e., a resource specification). Module 5470 is furtherrecursively created within module 5440, where module 5470 includesprocess logic that creates an instance of the resource entitled “ULL”(i.e., a resource specification). Module 5480 is further recursivelycreated within module 5440, where module 5480 includes process logicthat creates an instance of the resource entitled “AAA” (i.e., aresource specification). Thus, the modules that include the processlogic that creates instances of the various entities are createdmodularly and recursively.

FIG. 55 illustrates an example instance of a customer-facing service,according to an embodiment of the invention. The instance of thecustomer-facing service includes customer-facing service specification5510. The instance further includes a configuration of one or moreresource-facing service specifications and one or more resourcespecifications. More specifically, the instance of the customer-facingservice includes a configuration that includes resource-facing servicespecification 5520, resource specification 5530, resource specification5540, resource specification 5550, and resource specification 5560. Sucha configuration can be created by process logic contained within one ormore modules that are associated with each entity, as previouslydescribed.

FIG. 56 illustrates another flow diagram of the functionality of aservice design and order fulfillment module, according to anotherembodiment of the invention. The flow begins and proceeds to 5610. At5610, a service order is received, where the service order refers to anentity as its subject, where the entity includes metadata that defines acapability that is provided, and where the entity is composed of one ormore child entities. In certain embodiments, the subject entity is acustomer-facing service whose specification includes metadata thatdefines a service that is provided. Further, in some of theseembodiments, the one or more child entities include at least one of: aresource-facing service specification that includes metadata thatdefines a resource-facing service that is provided, or a resourcespecification that includes metadata that defines a resource that isprovided.

In certain embodiments, the service order includes at least one serviceorder line. In these embodiments, the at least one service order lineincludes at least one service action on the entity. Further, in certainembodiments, at least one child entity of the one or more child entitiesis a parent of another child entity of the one or more child entities.Additionally, in certain embodiments, the service order is an order forcommunication services. The flow then proceeds to 5620.

At 5620, a configuration is designed for the entity, where theconfiguration includes the entity, the one or more child entities, andone or more relationships between the entity and the one or more childentities. The flow then proceeds to 5630.

At 5630, for each child entity, a design context is created, where eachchild entity is a subject for the corresponding design context. Incertain embodiments, each design context includes a library of one ormore functions that support creation of one or more modules includingprocess logic that creates an instance of an entity. The flow thenproceeds to 5640.

At 5640, for each child entity, an instance of child entity is designedusing the corresponding design context. In certain embodiments, thedesigning the instance of the child entity is performed recursively foreach child entity. Further, in certain embodiments, the designing theinstance of the child entity is performed within a single configurationenvironment for each child entity. The flow then proceeds to 5650.

At 5650, for each child entity, a module is created that includesprocess logic that creates or updates an instance of the child entity.In certain embodiments, the process logic of each child entity isstructured using a uniform format. Further, in certain embodiments, thecreation of the module that includes process logic is performedrecursively for each child entity. The flow then ends.

Thus, in one embodiment, a service design and order fulfillment systemcan design a service instance by selecting and assembling one or moreentities that act as supporting components of the service instance. Thiscan support business agility be enabling rapid and low-risk redefinitionof products and services in both superficial and fundamental ways. Thiscan also simply the introduction of new services, as additions andchanges to the design logic can be kept to a minimum, and can followcomprehensible, repeatable, and predictable patterns.

The features, structures, or characteristics of the invention describedthroughout this specification may be combined in any suitable manner inone or more embodiments. For example, the usage of “one embodiment,”“some embodiments,” “certain embodiment,” “certain embodiments,” orother similar language, throughout this specification refers to the factthat a particular feature, structure, or characteristic described inconnection with the embodiment may be included in at least oneembodiment of the present invention. Thus, appearances of the phrases“one embodiment,” “some embodiments,” “a certain embodiment,” “certainembodiments,” or other similar language, throughout this specificationdo not necessarily all refer to the same group of embodiments, and thedescribed features, structures, or characteristics may be combined inany suitable manner in one or more embodiments.

One having ordinary skill in the art will readily understand that theinvention as discussed above may be practiced with steps in a differentorder, and/or with elements in configurations which are different thanthose which are disclosed. Therefore, although the invention has beendescribed based upon these preferred embodiments, it would be apparentto those of skill in the art that certain modifications, variations, andalternative constructions would be apparent, while remaining within thespirit and scope of the invention. In order to determine the metes andbounds of the invention, therefore, reference should be made to theappended claims.

We claim:
 1. A computer-readable medium having instructions stored thereon that, when executed by a processor, cause the processor to design a fulfillment solution and fulfill an order using the fulfillment solution, the designing and fulfilling comprising: defining a technical catalog that comprises one or more items comprising metadata used by a fulfillment solution; defining a fulfillment solution blueprint that comprises a plurality of order layers that define a plurality of layers of the fulfillment solution, a plurality of provider functions comprising a plurality of components of the fulfillment solution, and a plurality of interface contracts defining a plurality of interactions between a plurality of provider functions; designing the fulfillment solution to use at least one item of the one or more items of the technical catalog; designing the fulfillment solution based on the fulfillment solution blueprint; and generating the fulfillment solution based on the fulfillment solution blueprint using the at least one item of the one or more items of the technical catalog.
 2. The computer-readable medium of claim 1, wherein the defining the technical catalog further comprises: defining one or more entity model items comprising metadata that defines one of: an entity; or one or more attributes of an entity; defining one or more behavior model items comprising metadata that defines a behavior of an entity; and defining one or more infrastructure model items comprising metadata that defines a fulfillment topology.
 3. The computer-readable medium of claim 2, wherein the defining one or more entity model items further comprises defining at least one of: an entity comprising metadata that defines a capability that is provided; a relationship comprising metadata that defines an association between a first entity and a second entity; a mapping comprising metadata that defines an association between a first entity, one or more attributes of the first entity, or one or more attribute values of the first entity and a second entity, one or more attributes of the second entity, or one or more attribute values of the second entity; or an action comprising metadata that defines a pattern of a structured request to perform work on a subject.
 4. The computer-readable medium of claim 2, wherein the defining the one or more behavior model items further comprises defining at least one of: a fulfillment pattern comprising metadata that defines a set of one or more fulfillment functions and one or more dependencies; a transformation sequence comprising metadata that defines customizable process logic, wherein the customizable process logic is structured within one or more stages; or a static process comprising metadata that defines static process logic.
 5. The computer-readable medium of claim 2, wherein the defining the one or more infrastructure model items further comprises defining at least one of: an order specification comprising metadata that defines a structure of an order; a fulfillment function comprising metadata that defines a unit of fulfillment work provided by a fulfillment system; or a fulfillment topology comprising metadata that defines a set of one or more fulfillment systems.
 6. The computer-readable medium of claim 1, wherein the defining the fulfillment solution blueprint further comprises: defining a customer order layer for the fulfillment solution blueprint, wherein the customer order layer is configured to orchestrate a customer order and to transform the customer order into a service order; defining a service order layer for the fulfillment solution blueprint, wherein the service order layer is configured to orchestrate the service order and to transform the service order into a technical order; and defining a technical order layer for the fulfillment solution blueprint, wherein the technical order layer is configured to orchestrate the technical order.
 7. The computer-readable medium of claim 1, wherein the defining the fulfillment solution blueprint further comprises defining at least one of: a service order calculation provider function configured to transform a customer order into a service order; a service order orchestration provider function configured to receive a service order and generate an orchestration plan that fulfills the service order; a service order design and assign provider function configured to receive a service order and generate a service instance configuration based on the service order; a technical order calculation provider function configured to generate a technical order based on a configuration of resource-facing services and/or resources; a technical order orchestration provider function configured to receive a technical order and generate an orchestration plan that fulfills the technical order; or a technical order activation provider function configured to receive a technical order and translate the technical order into one or more command sequences delivered to one or more infrastructure elements.
 8. The computer-readable medium of claim 1, wherein the defining the fulfillment solution blueprint further comprises defining at least one of: a customer order comprising one or more customer order lines, wherein each customer order line comprises a product action and a product offering based on a product specification; a service order comprising one or more service order lines, wherein each service order line comprises a service action and a customer-facing service based on a customer-facing service specification; or a technical order comprising one or more technical order lines, wherein each technical order line comprises a technical action and a resource-facing service based on a resource-facing service specification or a resource based on a resource specification.
 9. The computer-readable medium of claim 1, wherein the defining the fulfillment solution blueprint further comprises defining at least one service design and order fulfillment system component to implement at least one provider function of at least one order layer of the fulfillment solution blueprint.
 10. The computer-readable medium of claim 1, wherein the designing the fulfillment solution based on the fulfillment solution blueprint further comprises designing the fulfillment solution to include the one or more provider functions of the fulfillment solution blueprint.
 11. A computer-implemented method for designing a fulfillment solution and fulfilling an order using the fulfillment solution, the computer-implemented method comprising: defining a technical catalog that comprises one or more items comprising metadata used by a fulfillment solution; defining a fulfillment solution blueprint that comprises a plurality of order layers that define a plurality of layers of the fulfillment solution, a plurality of provider functions comprising a plurality of components of the fulfillment solution, and a plurality of interface contracts defining a plurality of interactions between a plurality of provider functions; designing the fulfillment solution to use at least one item of the one or more items of the technical catalog; designing the fulfillment solution based on the fulfillment solution blueprint; and generating the fulfillment solution based on the fulfillment solution blueprint using the at least one item of the one or more items of the technical catalog.
 12. The computer-implemented method of claim 11, wherein the defining the technical catalog further comprises: defining one or more entity model items comprising metadata that defines one of: an entity; or one or more attributes of an entity; defining one or more behavior model items comprising metadata that defines a behavior of an entity; and defining one or more infrastructure model items comprising metadata that defines a fulfillment topology.
 13. The computer-implemented method of claim 12, wherein the defining one or more entity model items further comprises defining at least one of: an entity comprising metadata that defines a capability that is provided; a relationship comprising metadata that defines an association between a first entity and a second entity; a mapping comprising metadata that defines an association between a first entity, one or more attributes of the first entity, or one or more attribute values of the first entity and a second entity, one or more attributes of the second entity, or one or more attribute values of the second entity; or an action comprising metadata that defines a pattern of a structured request to perform work on a subject.
 14. The computer-implemented method of claim 11, wherein the defining the fulfillment solution blueprint further comprises: defining a customer order layer for the fulfillment solution blueprint, wherein the customer order layer is configured to orchestrate a customer order and to transform the customer order into a service order; defining a service order layer for the fulfillment solution blueprint, wherein the service order layer is configured to orchestrate the service order and to transform the service order into a technical order; and defining a technical order layer for the fulfillment solution blueprint, wherein the technical order layer is configured to orchestrate the technical order.
 15. The computer-implemented method of claim 11, wherein the defining the fulfillment solution blueprint further comprises defining at least one of: a service order calculation provider function configured to transform a customer order into a service order; a service order orchestration provider function configured to receive a service order and generate an orchestration plan that fulfills the service order; a service order design and assign provider function configured to receive a service order and generate a service instance configuration based on the service order; a technical order calculation provider function configured to generate a technical order based on a configuration of resource-facing services and/or resources; a technical order orchestration provider function configured to receive a technical order and generate an orchestration plan that fulfills the technical order; or a technical order activation provider function configured to receive a technical order and translate the technical order into one or more command sequences delivered to one or more infrastructure elements.
 16. A system, comprising: a technical catalog definition module configured to define a technical catalog that comprises one or more items comprising metadata used by a fulfillment solution; a fulfillment solution blueprint definition module configured to define a fulfillment solution blueprint that comprises a plurality of order layers that define a plurality of layers of the fulfillment solution, a plurality of provider functions comprising a plurality of components of the fulfillment solution, and a plurality of interface contracts defining a plurality of interactions between a plurality of provider functions; a fulfillment solution design module configured to design the fulfillment solution to use at least one item of the one or more items of the technical catalog; wherein the fulfillment solution design module is further configured to design the fulfillment solution based on the fulfillment solution blueprint; and a fulfillment solution generation module configured to generate the fulfillment solution based on the fulfillment solution blueprint using the at least one item of the one or more items of the technical catalog.
 17. The system of claim 16, wherein the technical catalog definition module is further configured to define one or more entity model items comprising metadata that defines one of: an entity; or one or more attributes of an entity; wherein the technical catalog definition module is further configured to define one or more behavior model items comprising metadata that defines a behavior of an entity; and wherein the technical catalog definition module is further configured to define one or more infrastructure model items comprising metadata that defines a fulfillment topology.
 18. The system of claim 16, wherein the technical catalog definition module is further configured to define an entity comprising metadata that defines a capability that is provided; wherein the technical catalog definition module is further configured to define a relationship comprising metadata that defines an association between a first entity and a second entity; wherein the technical catalog definition module is further configured to define a mapping comprising metadata that defines an association between a first entity, one or more attributes of the first entity, or one or more attribute values of the first entity and a second entity, one or more attributes of the second entity, or one or more attribute values of the second entity; and wherein the technical catalog definition module is further configured to define an action comprising metadata that defines a pattern of a structured request to perform work on a subject.
 19. The system of claim 16, wherein the fulfillment solution blueprint definition module is further configured to define a customer order layer for the fulfillment solution blueprint, wherein the customer order layer is configured to orchestrate a customer order and to transform the customer order into a service order; wherein the fulfillment solution blueprint definition module is further configured to define a service order layer for the fulfillment solution blueprint, wherein the service order layer is configured to orchestrate the service order and to transform the service order into a technical order; and wherein the fulfillment solution blueprint definition module is further configured to define a technical order layer for the fulfillment solution blueprint, wherein the technical order layer is configured to orchestrate the technical order.
 20. The system of claim 16, wherein the fulfillment solution blueprint definition module is further configured to define a service order calculation provider function configured to transform a customer order into a service order; wherein the fulfillment solution blueprint definition module is further configured to define a service order orchestration provider function configured to receive a service order and generate an orchestration plan that fulfills the service order; wherein the fulfillment solution blueprint definition module is further configured to define a service order design and assign provider function configured to receive a service order and generate a service instance configuration based on the service order; wherein the fulfillment solution blueprint definition module is further configured to define a technical order calculation provider function configured to generate a technical order based on a configuration of resource-facing services and/or resources; wherein the fulfillment solution blueprint definition module is further configured to define a technical order orchestration provider function configured to receive a technical order and generate an orchestration plan that fulfills the technical order; and wherein the fulfillment solution blueprint definition module is further configured to define a technical order activation provider function configured to receive a technical order and translate the technical order into one or more command sequences delivered to one or more infrastructure elements. 